|
|
BugTraq
GNU/Linux 'info Buffer Overflow Aug 06 2004 12:46AM Josh Martin (skizzles gmail com) (3 replies) Re: GNU/Linux 'info Buffer Overflow Aug 06 2004 11:09PM Roman Werpachowski (roman student ifpan edu pl) Re: GNU/Linux 'info Buffer Overflow Aug 06 2004 09:41PM Niels Bakker (niels-bugtraq bakker net) (1 replies) Re: GNU/Linux 'info Buffer Overflow Aug 07 2004 03:31PM Janusz A. Urbanowicz (alex syjon fantastyka net) |
|
Privacy Statement |
> Package: info
> Version: 4.7-2.1
> Severity: grave
> Tags: security
> Justification: user security hole
> This buffer overflow is very trivial to leverage as there are several
> bytes available (10-15+). It may be possible that arbitary system calls
> could be made though this hole. It is also possible to leverage this
> from the command line using the --restore=FILENAME flag, and need not
> have the program running. Although it is not running as suid, or as a
> daemon, in a case where info is being used as a public service, it may
> be a security problem.
Well.. it may be a problem if you can convince root (or somebody else not
yourself) to go to an 'info' page and enter 'f' and 225 bytes and hit return,
or to convince root to run a 'info --restore=' command. Barring that,
I'm failing to see how it's a "grave" severity - unless there's a way to leverage
it or social-engineer it that I'm missing, if this is "grave" then *every* bug that
results in a SIGSEGV is grave.....
[ reply ]