Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 19 Apr 2015 10:15:41 -0700
From: Michal Zalewski <>
To: oss-security <>
Subject: Re: libxml2 issue: out-of-bounds memory access when
 parsing an unclosed HTML comment

Uh, so I guess we could also mention this one:

I wasn't sure it would ever cause anything serious / interesting,
though. Perhaps for some exotic uses?


On Sun, Apr 19, 2015 at 10:11 AM, Reed Loden <> wrote:
> (saw this randomly today on Twitter, so figured I'd send it on to make sure
> it gets a CVE and actually gets fixed)
> """
> This is an out-of-bounds memory access in libxml2. By entering a unclosed
> html comment such as <!-- the libxml2 parser didn't stop parsing at the end
> of the buffer, causing random memory to be included in the parsed comment
> that was returned to ruby. In Shopify, this caused ruby objects from
> previous http requests to be disclosed in the rendered page.
> Link to the issue in libxml2's bugtracker:
> A patched version of nokogiri (which uses a embedded libxml2) is available
> here:
> This bug is still not patched upstream, but both libxml2 and nokogiri
> developers are aware of the issue.
> """
> ~reed

Powered by blists - more mailing lists

Your e-mail address:

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

Powered by Openwall GNU/*/Linux - Powered by OpenVZ