Re:Don't run 'strings' on untrusted files
by greenyoda on Saturday October 25, 2014 @01:34PM
(#8508788)
I don't think so. "file" only needs to read the first few bytes at the beginning of a file to guess what type of file it is, so it isn't likely to have any buffer overflow problems.
[ Parent
| on HN ]
Re:Don't run 'strings' on untrusted files
by _delirium on Saturday October 25, 2014 @02:05PM
(#8508878)
You might think so, but 'file' has its share of buffer overflows, integer overflows, attacker-inducible infinite loops, etc. It does some more extensive parsing for some kinds of files, and some of those end up with edge cases. Here's one from two days ago, a buffer overrun in parsing ELF files: https://access.redhat.com/security/cve/CVE-2014-3710. Others: https://security-tracker.debian.org/tracker/source-package/f...