Bug 1340016 (CVE-2016-1683) - CVE-2016-1683 chromium-browser: out-of-bounds access in libxslt
Summary: CVE-2016-1683 chromium-browser: out-of-bounds access in libxslt
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2016-1683
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1340131 1340132 1349705 1349706 1349707
Blocks: 1340055
TreeView+ depends on / blocked
 
Reported: 2016-05-26 10:38 UTC by Adam Mariš
Modified: 2021-02-17 03:50 UTC (History)
2 users (show)

Fixed In Version: Chrome 51.0.2704.63
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-24 05:01:22 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1190 0 normal SHIPPED_LIVE Important: chromium-browser security update 2016-06-01 14:50:06 UTC

Description Adam Mariš 2016-05-26 10:38:18 UTC 
An out-of-bounds access flaw was found in the libxslt component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=583156

External References:

http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html
Comment 2 errata-xmlrpc 2016-06-01 10:52:10 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2016:1190 https://access.redhat.com/errata/RHSA-2016:1190
Comment 3 Huzaifa S. Sidhpurwala 2016-06-03 04:56:34 UTC 
Upstream commit:

https://git.gnome.org/browse/libxslt/commit/?id=d182d8f6ba3071503d96ce17395c9d55871f0242
Comment 4 Huzaifa S. Sidhpurwala 2016-06-24 04:49:44 UTC 
Created libxslt tracking bugs for this issue:

Affects: fedora-all [bug 1349705]
Comment 5 Huzaifa S. Sidhpurwala 2016-06-24 05:00:21 UTC 
Created mingw-libxslt tracking bugs for this issue:

Affects: fedora-all [bug 1349706]
Affects: epel-7 [bug 1349707]
Note You need to log in before you can comment on or make changes to this bug.