New issue
Advanced search Search tips

Issue 816860 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 722079
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Security



Sign in to add a comment

Chromium: Vulnerability reported in libxml

Project Member Reported by vomit.go...@appspot.gserviceaccount.com, Feb 27 2018

Issue description

Automated analysis has detected that the following third party packages have had vulnerabilities publicly reported. 

NOTE: There may be several bugs listed below - in almost all cases, all bugs can be quickly addressed by upgrading to the latest version of the package.

Package Name: libxml
Package Version: [cpe:/a:xmlsoft:libxml2:2.7.7]

Advisory: CVE-2017-5130
  Details: https://vomit.googleplex.com/advisory?id=CVE/CVE-2017-5130
  CVSS severity score: 6.8/10.0
  Confidence: high
  Description:

An integer overflow in xmlmemory.c in libxml2 before 2.9.5, as used in Google Chrome prior to 62.0.3202.62 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted XML file.


 
Cc: tkent@chromium.org
Components: Blink>XML
The upstream bug references  crbug.com/722079  with a landed patch https://chromium-review.googlesource.com/c/chromium/src/+/535233, so it's not clear whether we're actually vulnerable here.

Comment 2 by kenrb@chromium.org, Feb 28 2018

Mergedinto: 722079
Status: Duplicate (was: Unconfirmed)
The text in the report contains "as used in Google Chrome prior to 62.0.3202.62", which aligns with rolling libxml on the other bug. I can't think of any reason why we might want to keep this open.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 7 2018

Labels: -Restrict-View-SecurityTeam allpublic
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment