A buffer overflow in UnZip 5.50 and earlier allows local users to execute
arbitrary code via a long filename command line argument. NOTE: since the
overflow occurs in a non-setuid program, there are not many scenarios under
which it poses a vulnerability, unless unzip is passed long arguments when
it is invoked from other programs.
Posted Feb 9, 2006 20:39 UTC (Thu) by roelofs (subscriber, #2599)
[Link]
... i.e., 5.52 and earlier, as demonstrated in the full-disclosure thread. Looks like it's actually the error-message buffer (reused sliding-window buffer) that's overflowing, in part because the filename is printed three times in that particular message ("foo", "foo.zip", "foo.ZIP").
Fortunately, tcsh doesn't support words that long. Bash-users are hosed, though. ;-)