full-disclosure - Re: QFTP (LIBFtp 3.1-1) (command line) sprintf() local buffer overflow

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 16 Mar 2007 08:25:20 +0100
From: "starcadi starcadi" <starcadi@...il.com>
To: "Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: QFTP (LIBFtp 3.1-1) (command line) sprintf()
	local buffer overflow

i know but the security argument in general term comprise too this type.

2007/3/16, Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu>:
> On Thu, 15 Mar 2007 21:12:50 BST, =?ISO-8859-1?Q?Knud_Erik_H=F8jgaard?= said:
> > On 3/15/07, starcadi starcadi <starcadi@...il.com> wrote:
> >
> > > >> POC
> > yes, piece of crap. Who cares about local overflows in non-suid applications?
>
> It can be interesting if you can find a way to get some *other* user to
> run the application - so if you can find a web server that has a CGI that
> invokes QFTP (or whatever) with attacker-controlled parameters, you can use
> that to pwn the webserver.  Basically, you need to be able to leverage the
> distinction between "yourself" and "the userid executing the program".
>
>


-- 
~ starcadi

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/