full-disclosure - Re: Fwd: VSFTPD Remote Heap Overrun (low severity)

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]

Message-ID: <11d0cd2b-84b1-4f3a-829d-b0396cab873b@zmail15.collab.prod.int.phx2.redhat.com>
Date: Tue, 13 Dec 2011 19:58:12 -0500 (EST)
From: Ramon de C Valle <rcvalle@...hat.com>
To: Daniel J Walsh <dwalsh@...hat.com>
Cc: "HI-TECH ." <isowarez.isowarez.isowarez@...glemail.com>,
	full-disclosure@...ts.grok.org.uk
Subject: Re: Fwd: VSFTPD Remote Heap Overrun (low severity)



> If you want to prevent apps from reading zoneinfo files that a user
> can write and read files a user can write, you will loose.
> 
> Why are you setting up the chroot with content a user can write too?
> If you simply prevent him from writing to /usr/share, won't that
> solve
> the problem?
Not really. Because, in fact, the user, when chrooted, is writing to /home/user/usr/share/zoneinfo/. I've suggested a different file context for /home/(.*)/usr/share/zoneinfo(/.*) in vsftpd policy module. But I don't think this will be necessary due to the recent findings about vsftpd.

-- 
Ramon de C Valle / Red Hat Security Response Team

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