Bug 1503537 (CVE-2017-5130)

Summary:	CVE-2017-5130 chromium-browser: heap overflow in libxml2
Product:	[Other] Security Response	Reporter:	Martin Prpič <mprpic>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	bmcclain, cfergeau, csutherl, dblechte, eedri, gzaronik, huzaifas, jclere, lgao, lsurette, mbabacek, mgoldboi, michal.skrivanek, myarboro, nb, ohudlick, rbalakri, rh-spice-bugs, sherold, sparks, srevivo, tcallawa, tpopela, twalsh, veillard, weli, yaneti, ykaul, ylavi
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	chromium-browser 62.0.3202.62	Doc Type:	If docs needed, set a value
Doc Text:	A heap overflow flaw was found in the libxml2 library. An application compiled with libxml2 using the vulnerable debug-only function xmlMemoryStrdup could be used by an attacker to crash the application or execute arbitrary code with the permission of the user running the application.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-30 05:48:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1503551, 1503557, 1503558
Bug Blocks:	1504612

Description Martin Prpič 2017-10-18 11:41:37 UTC

A heap overflow flaw was found in the libxml2 component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html

Comment 1 Martin Prpič 2017-10-18 11:44:31 UTC

Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1503551]

Comment 4 errata-xmlrpc 2017-10-20 08:41:00 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2017:2997 https://access.redhat.com/errata/RHSA-2017:2997

Comment 5 Huzaifa S. Sidhpurwala 2017-10-30 05:39:13 UTC

The affected function xmlMemoryStrdup() is a debug-only function that should never be called in production builds. The only exception is xmllint when invoked with --maxmem. The same issue applies to

xmlMallocLoc
xmlReallocLoc

This issue is fixed via the following upstream commit:

https://git.gnome.org/browse/libxml2/commit/?id=897dffbae322b46b83f99a607d527058a72c51ed

Referenced at:

https://bugzilla.gnome.org/show_bug.cgi?id=783026 (currently private)

Comment 9 Eric Christensen 2019-06-28 13:31:04 UTC

Statement:

This issue does not affect the libxml library shipped with Red Hat Enterprise Linux because the affected code xmlMemoryStrdup() is a debug-only function that should never be called in production builds. The only exception is xmllint when invoked with --maxmem. The same issue applies to the other two affected functions namely xmlMallocLoc and xmlReallocLoc.