Issue 43307 in oss-fuzz: elfutils:fuzz-dwfl-core: Crash in read_addrs

[ClusterFuzz-External via monorail]

Status: New
Owner: ----
CC: elfut...@sourceware.org, evv...@gmail.com, izzeem@google.com 
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Security_Severity-Medium Proj-elfutils Reported-2022-01-04
Type: Bug-Security

New issue 43307 by ClusterFuzz-External: elfutils:fuzz-dwfl-core: Crash in read_addrs
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43307

Detailed Report: https://oss-fuzz.com/testcase?key=4696722113167360

Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-dwfl-core
Job Type: libfuzzer_asan_i386_elfutils
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0xf75b3fe0
Crash State:
  read_addrs
  dwfl_link_map_report
  dwfl_core_file_report
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_i386_elfutils&revision=202201040606

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4696722113167360

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.