From: "da… via monorail" <monorail+v2.1355924921@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45630 in oss-fuzz: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str
Date: Sun, 20 Mar 2022 02:57:07 -0700 [thread overview]
Message-ID: <00000000000019a08705daa36700@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=ea1264b8eb8555aa9de8bbd022f3db6f=oss-fuzz@monorail-prod.appspotmail.com>
Comment #2 on issue 45630 by da...@adalogics.com: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c2
MSAN report:
Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-ecd598ded30b07196a2ab343f59f7a25442f0560
==744==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x538d7b in validate_str /src/elfutils/libelf/elf_strptr.c:61:4
#1 0x5383fe in elf_strptr /src/elfutils/libelf/elf_strptr.c:188:11
#2 0x527361 in fuzz_logic_one /src/fuzz-libelf.c:37:26
#3 0x527cec in LLVMFuzzerTestOneInput /src/fuzz-libelf.c:82:3
#4 0x4551d2 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:611:15
#5 0x440d82 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#6 0x4465ec in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:9
#7 0x46ef82 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#8 0x7fd73ce3f0b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#9 0x41f4cd in _start
Uninitialized value was created by a heap allocation
#0 0x4d49ad in __interceptor_malloc /src/llvm-project/compiler-rt/lib/msan/msan_interceptors.cpp:911:3
#1 0x53feb1 in __libelf_decompress /src/elfutils/libelf/elf_compress.c:227:19
#2 0x5408d7 in __libelf_decompress_elf /src/elfutils/libelf/elf_compress.c:300:19
#3 0x538903 in get_zdata /src/elfutils/libelf/elf_strptr.c:45:17
#4 0x537c19 in elf_strptr /src/elfutils/libelf/elf_strptr.c:135:38
#5 0x527361 in fuzz_logic_one /src/fuzz-libelf.c:37:26
#6 0x527cec in LLVMFuzzerTestOneInput /src/fuzz-libelf.c:82:3
#7 0x4551d2 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:611:15
#8 0x440d82 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#9 0x4465ec in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:9
#10 0x46ef82 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#11 0x7fd73ce3f0b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
--
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.
next prev parent reply other threads:[~2022-03-20 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ea1264b8eb8555aa9de8bbd022f3db6f=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 5:50 ` ClusterFuzz-External via monorail
2022-03-19 22:53 ` ClusterFuzz-External via monorail
2022-03-20 9:57 ` da… via monorail [this message]
2022-03-20 9:57 ` da… via monorail
2022-03-21 3:23 ` evv… via monorail
2022-03-24 21:06 ` ClusterFuzz-External via monorail
2022-04-06 15:28 ` ClusterFuzz-External via monorail
2022-04-06 15:29 ` ClusterFuzz-External via monorail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000019a08705daa36700@google.com \
--to=monorail+v2.1355924921@chromium.org \
--cc=elfutils-devel@sourceware.org \
--cc=oss-fuzz@monorail-prod.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).