Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sun, 19 Apr 2015 10:11:58 -0700
From: Reed Loden <>
	Assign a CVE Identifier <>
Subject: libxml2 issue: out-of-bounds memory access when parsing an unclosed
 HTML comment

(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

This bug is still not patched upstream, but both libxml2 and nokogiri
developers are aware of the issue.


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.