From: Alexander Cherepanov <cherepan@mccme.ru>
To: elfutils-devel@lists.fedorahosted.org
Subject: Fuzzing elfutils
Date: Wed, 03 Dec 2014 18:16:29 +0300 [thread overview]
Message-ID: <547F294D.5010807@mccme.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
Hi!
[Please Cc me, I'm not subscribed.]
I've been fuzzing binutils for some time now and I've spotted that you
are also intersted in it. So I have tried to fuzz elfutils. Results
attached. valgrind logs or gdb backtraces are included. Cases are
deduplicated based on the full stacktrackes as provided by the
corresponding tools.
I'm not very familiar with elfutils. Which commands give the most code
coverage (and shortest run time)? I've used two commands so far:
objdump -rs
readelf -aAdehIlnrsSVcp -w
and crashes seem to differ for them.
BTW does indended use of elfutils include the use against untrusted
files and do you track corresponding security issues?
Any feedback is welcome.
Contents:
objdump-crashes.tar.gz:
Files: 11
Errors:
10 Invalid read of size ...
7 Process terminating with default action of signal 11 (SIGSEGV)
3 Process terminating with default action of signal 8 (SIGFPE)
readelf-crashes.tar.gz:
Files: 11
Errors:
1 Argument 'size' of function malloc has a fishy (possibly
negative) value: ...
1 Invalid free() / delete / delete[] / realloc()
9 Invalid read of size ...
6 Process terminating with default action of signal 11 (SIGSEGV)
1 Process terminating with default action of signal 8 (SIGFPE)
readelf-asserts.tar.gz:
Files: 2
Errors:
1 No assertion info in gdb backtrace.
1 readelf.c:7731: print_debug_exception_table: Assertion `readp
== action_table' failed.
--
Alexander Cherepanov
[-- Attachment #2: objdump-crashes.tar.gz --]
[-- Type: application/x-gzip, Size: 945323 bytes --]
[-- Attachment #3: readelf-crashes.tar.gz --]
[-- Type: application/x-gzip, Size: 74477 bytes --]
[-- Attachment #4: readelf-asserts.tar.gz --]
[-- Type: application/x-gzip, Size: 934473 bytes --]
next reply other threads:[~2014-12-03 15:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 15:16 Alexander Cherepanov [this message]
2014-12-04 14:27 Mark Wielaard
2014-12-04 16:03 Mark Wielaard
2014-12-04 23:10 Alexander Cherepanov
2014-12-05 8:58 Mark Wielaard
2014-12-08 1:01 Alexander Cherepanov
2014-12-08 3:06 Alexander Cherepanov
2014-12-08 8:52 Mark Wielaard
2014-12-08 9:14 Mark Wielaard
2014-12-12 12:08 Mark Wielaard
2014-12-18 18:15 Alexander Cherepanov
2014-12-19 0:13 Mark Wielaard
2014-12-21 22:20 Alexander Cherepanov
2014-12-23 11:42 Mark Wielaard
2014-12-29 3:16 Alexander Cherepanov
2014-12-31 11:03 Mark Wielaard
[not found] <199C1200-40AC-4AD2-89D4-24E172CBA353@catenacyber.fr>
2022-10-21 12:58 ` Philippe Antoine
2022-10-21 13:22 ` Frank Ch. Eigler
2022-10-21 19:57 ` Evgeny Vereshchagin
2022-10-22 9:27 ` Philippe Antoine
2022-10-22 10:21 ` Evgeny Vereshchagin
2022-10-21 13:33 ` Evgeny Vereshchagin
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=547F294D.5010807@mccme.ru \
--to=cherepan@mccme.ru \
--cc=elfutils-devel@lists.fedorahosted.org \
/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).