Bug#779397: xterm: buffer overflow with -S option
On 2015-03-02 02:38 +0100, Vincent Lefevre wrote:
> Moreover it happens that here the buffer overflow was detected
> immediately,
Which has apparently been the case for over three years, since I can
reproduce the problem with wheezy's xterm. This probably means that
very few people use this obscure option.
> but problems may be more important if xterm continued
> with corrupted memory and uncontrolled effects.
Might happen if xterm is built without -D_FORTIFY_SOURCE=2. The squeeze
version does not crash immediately, haven't looked if there were any
code changes in that area between squeeze and wheezy.
Cheers,
Sven
Reply to: