[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240728143758.GA17036@openwall.com>
Date: Sun, 28 Jul 2024 16:37:58 +0200
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Cc: sebastian@...tricular.com
Subject: Re: GStreamer Security Advisory 2024-0003: Orc compiler stack-based buffer overflow
On Fri, Jul 26, 2024 at 01:05:09PM -0700, Alan Coopersmith wrote:
> Yes, this came up in the discussion to add asprintf() to POSIX in
> https://austingroupbugs.net/view.php?id=1496 :
>
> >Of the above listed implementations, all but GNU libc document that they
> >will
> >set *ptr to NULL on error, while GNU libc explicitly states that you cannot
> >rely on it to do so (and looking at its code, sometimes it does, sometimes
> >it doesn't).
>
> and so the standard was written to allow both ways to be conformant.
>
> If GNU libc was willing to change that, perhaps the next version of the
> standard could as well.
I didn't know you contributed to getting this standardized. Thank you!
I think glibc should change, but the standard should merely strongly
encourage libc's to implement the safer behavior. It shouldn't
guarantee it because older glibc systems will remain in use.
Alexander
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.
