Bug 8666 - ash: Segmentation fault trapcmd (fuzzing)
Summary: ash: Segmentation fault trapcmd (fuzzing)
Status: RESOLVED DUPLICATE of bug 8661
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.24.x
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-09 16:05 UTC by Fernando Muñoz
Modified: 2016-02-13 03:31 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
crashing test (380 bytes, application/x-shellscript)
2016-02-09 16:05 UTC, Fernando Muñoz 		Details
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 Fernando Muñoz 2016-02-09 16:05:30 UTC 
Created attachment 6306 [details]
crashing test

Current config:
https://paste.kde.org/pbsgwk4ob

(gdb) run sh fuzzed.sh 
Starting program: /root/fuzzshell/busybox_unstripped sh fuzzed.sh
fuzzed.sh: trap: line 1: USR340282366920938463463374607431768211456: invalid signal specification

Program received signal SIGSEGV, Segmentation fault.
0x0808bac5 in trapcmd ()
(gdb) bt
#0  0x0808bac5 in trapcmd ()
#1  0x00000000 in ?? ()

Valgrind reports

==15131== Invalid read of size 4
==15131==    at 0x808BAC5: trapcmd (in /root/fuzzshell/busybox_unstripped)
==15131==  Address 0x6ba9240c is not stack'd, malloc'd or (recently) free'd
Comment 1 Mike Frysinger 2016-02-13 03:31:21 UTC 
pretty sure it's just the same as bug 8661

*** This bug has been marked as a duplicate of bug 8661 ***