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] [thread-next>] [day] [month] [year] [list]

Date: Mon, 12 Dec 2011 23:27:04 +0000
From: lists@...atla.org.uk
To: Valdis.Kletnieks@...edu, rcvalle@...hat.com
Cc: isowarez.isowarez.isowarez@...glemail.com, dwalsh@...hat.com,
	full-disclosure@...ts.grok.org.uk
Subject: Re: Fwd: VSFTPD Remote Heap Overrun (low severity)

Valdis.Kletnieks vt.edu:

> The problem is that at open() time, there's no good way to specify what the
> expected label is (now *that* might be an interesting extention to open() for
> some enterprisng grad student) - so as long as the file has *any* foo_t label
> that the program is allowed to access, the open() will succeed.  There's no way
> for it to say "I'm opening what *should* be a locale_t file, so if I'm being
> coerced into opening a user_foo_t, please nuke the request".

That sounds like a "confused deputy".
http://www.cis.upenn.edu/~KeyKOS/ConfusedDeputy.html

Is it reasonable to obtain all timezone data at program startup and
refuse to open locale-related files after chroot?

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