Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 31 Aug 2010 16:02:14 -0400 (EDT)
From: "Steven M. Christey" <>
To: Josh Bressers <>
Subject: Re: CVE id request: libc fortify source information

I think this technically qualifies as an "exposure" which is the "E" in 
"CVE" - it can be used as a stepping stone for exploitation of another 
vulnerability.  (Very old, unwieldy definitions here:

The risk may be very minimal, but the FORTIFY_SOURCE protection mechanism 
is not working "as advertised" - it can be manipulated for an 
admittedly-small information leak.

Use CVE-2010-3192 for the issue.

- Steve

On Tue, 31 Aug 2010, Josh Bressers wrote:

> ----- "Nico Golde" <> wrote:
>> Hi,
>> did this ever get a CVE id? As this also works for setuid programs it
>> would be
>> nice to get one assigned and have this patched.
> Steve,
> What is MITRE policy on this one. By itself I question if this is a
> security flaw, but it also would appear to have the potential to turn a DoS
> into something worse.
> I'm not sure what policy is in this instance.
> Thanks.
> --
>    JB

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.