* [Bug libdw/23753] New: Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC
@ 2018-10-10 9:32 wcventure at 126 dot com
2018-10-10 9:35 ` [Bug libdw/23753] " wcventure at 126 dot com
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: wcventure at 126 dot com @ 2018-10-10 9:32 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=23753
Bug ID: 23753
Summary: Invalid Address Read problem in
dwfl_segment_report_module.c when executing ./eu-stack
--core=$POC
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libdw
Assignee: unassigned at sourceware dot org
Reporter: wcventure at 126 dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Hi there,
Our fuzzer caught Invalid Address Read problem in eu-stack of the latest
elfutils-0.174 code base, this inputs will cause the segment faults and I have
confirmed them with address sanitizer too. Please use the "./eu-stack
--core=$POC" or "./eu-stack --core=$POC -abdilmsv" to reproduce the bug. If you
have any questions, please let me know.
The ASAN dumps the stack trace as follows:
ASAN:DEADLYSIGNAL
=================================================================
==9753==ERROR: AddressSanitizer: SEGV on unknown address 0x7f6afb9ac114 (pc
0x7f6afa17a7dc bp 0x7fffc8bb1900 sp 0x7fffc8bb17f0 T0)
==9753==The signal is caused by a READ memory access.
#0 0x7f6afa17a7db in consider_notes
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:486
#1 0x7f6afa17accc in consider_phdr
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:529
#2 0x7f6afa176fa2 in dwfl_segment_report_module
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:590
#3 0x7f6afa185ce0 in dwfl_core_file_report
/elfutils-0.174/libdwfl/core-file.c:541
#4 0x405106 in parse_opt /elfutils-0.174/src/stack.c:590
#5 0x7f6af9a64847 in argp_parse (/lib/x86_64-linux-gnu/libc.so.6+0x114847)
#6 0x4056a7 in main /elfutils-0.174/src/stack.c:690
#7 0x7f6af997082f in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
#8 0x402308 in _start (/elfutils-0.174/build/bin/eu-stack+0x402308)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:486 in consider_notes
==9753==ABORTING
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libdw/23753] Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC
2018-10-10 9:32 [Bug libdw/23753] New: Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC wcventure at 126 dot com
@ 2018-10-10 9:35 ` wcventure at 126 dot com
2018-10-14 15:03 ` mark at klomp dot org
2018-10-14 16:22 ` wcventure at 126 dot com
2 siblings, 0 replies; 4+ messages in thread
From: wcventure at 126 dot com @ 2018-10-10 9:35 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=23753
--- Comment #1 from wcventure <wcventure at 126 dot com> ---
Created attachment 11307
--> https://sourceware.org/bugzilla/attachment.cgi?id=11307&action=edit
POC-stack
./eu-stack --core=$POC
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libdw/23753] Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC
2018-10-10 9:32 [Bug libdw/23753] New: Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC wcventure at 126 dot com
2018-10-10 9:35 ` [Bug libdw/23753] " wcventure at 126 dot com
@ 2018-10-14 15:03 ` mark at klomp dot org
2018-10-14 16:22 ` wcventure at 126 dot com
2 siblings, 0 replies; 4+ messages in thread
From: mark at klomp dot org @ 2018-10-14 15:03 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=23753
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |mark at klomp dot org
Resolution|--- |DUPLICATE
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Same as bug #23752.
*** This bug has been marked as a duplicate of bug 23752 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libdw/23753] Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC
2018-10-10 9:32 [Bug libdw/23753] New: Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC wcventure at 126 dot com
2018-10-10 9:35 ` [Bug libdw/23753] " wcventure at 126 dot com
2018-10-14 15:03 ` mark at klomp dot org
@ 2018-10-14 16:22 ` wcventure at 126 dot com
2 siblings, 0 replies; 4+ messages in thread
From: wcventure at 126 dot com @ 2018-10-14 16:22 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=23753
--- Comment #3 from wcventure <wcventure at 126 dot com> ---
Thanks for paying attention to this problem and proposing to fix it in time.
This bug was discovered by NTU Cyber-Security-Lab, for fuzzing research work.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-10-14 16:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-10 9:32 [Bug libdw/23753] New: Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC wcventure at 126 dot com
2018-10-10 9:35 ` [Bug libdw/23753] " wcventure at 126 dot com
2018-10-14 15:03 ` mark at klomp dot org
2018-10-14 16:22 ` wcventure at 126 dot com
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).