Bug 24705 - OOM in objdump when provided with fuzzed linux x86-64 elf samples
Summary: OOM in objdump when provided with fuzzed linux x86-64 elf samples
Status: RESOLVED OBSOLETE
Alias: None
Product: binutils
Classification: Unclassified
Component: binutils (show other bugs)
Version: 2.32
: P2 minor
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-19 17:06 UTC by Eunsoo Sheen
Modified: 2019-06-20 13:06 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
input files which raise OOM error in objdump (50.41 KB, application/x-gzip)
2019-06-19 17:06 UTC, Eunsoo Sheen 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eunsoo Sheen 2019-06-19 17:06:30 UTC 
Created attachment 11849 [details]
input files which raise OOM error in objdump

I tested objdump in binutils-2.32 with some fuzzed samples.

These samples have objdump raise out of memory error.

Error message is as follows:

~$ objdump -x ./crashes/id\:000000\,sig\:06\,src\:000008\,op\:havoc\,rep\:8

./new-test/crashes/id:000000,sig:06,src:000008,op:havoc,rep:8:     file format elf64-x86-64
./new-test/crashes/id:000000,sig:06,src:000008,op:havoc,rep:8
architecture: i386:x86-64, flags 0x00000011:
HAS_RELOC, HAS_SYMS
start address 0x0000000000000000

objdump: out of memory allocating 355045037616 bytes after a total of 0 bytes
Comment 1 Eunsoo Sheen 2019-06-20 13:06:12 UTC 
It is not a bug of objdump.