Date: Tue, 25 Jan 2011 08:57:39 -0800 From: Kees Cook <kees@...flux.net> To: oss-security@...ts.openwall.com Cc: coley <coley@...re.org>, Pierre Joye <pierre.php@...il.com> Subject: Re: CVE request: libxml2 heap contents leak If it's a requirement that "xmlChar *" be valid null-terminated utf8, then I'd agree it seems this is PHP's responsibility. Are there perhaps other places where this needs to be checked besides just with xmlTextWriterWriteAttribute()? On Tue, Jan 25, 2011 at 05:45:48PM +0100, Pierre Joye wrote: > Btw, I re opened the php one as Daniel seems to think that it is the > application responsibility and not libxml. I'm not totally convinced > and I asked Rob to check this problem again. > > On Mon, Jan 24, 2011 at 10:41 PM, Kees Cook <kees@...ntu.com> wrote: > > Hello, > > > > I'd like to get a CVE assigned for a minor heap contents leak in > > libxml2. I reported that it is possible to leak heap memory contents > > from libxml2 (and things linked against it, for example PHP, or things > > written in PHP): > > > > https://bugzilla.gnome.org/show_bug.cgi?id=631551 > > > > Thanks, > > > > -Kees > > > >  http://bugs.php.net/bug.php?id=52998 > >  http://status.net/open-source/issues/2798 > > > > -- > > Kees Cook > > Ubuntu Security Team > > > > > > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- Kees Cook @outflux.net
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.