Created attachment 7844 [details]
strings crasher 1
Attached are two samples that cause the strings tool to segfault. The first one has been found by Michal Zalewski and postet on twitter:
Here's how he described the issue on oss-security:
"The immediate cause is due to srec_scan() in srec.c decreasing 'bytes'
without range checking until it wraps around. The already-bad value of
'bytes' is assigned to 'sec->size' few lines before the crash, so
perhaps there would be potential for exploitability later down the
line; but the code ends up crashing soon thereafter in a 'while (bytes
> 0)' loop that has no other exit conditions. That loop would need to
go over the entire address space without SEGV to avoid the crash."
In reply to that someone else postet another crasher to oss-security that seems to expose a different code path.
Here's the corresponding thread:
Created attachment 7845 [details]
strings crasher 2
this was already fixed months ago and is included in the pending 2.25 release