Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1503537 - (CVE-2017-5130) CVE-2017-5130 chromium-browser: heap overflow in libxml2
CVE-2017-5130 chromium-browser: heap overflow in libxml2
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20171017,repo...
: Security
Depends On: 1503551 1503557 1503558
Blocks: 1504612
  Show dependency tree / graph
 
Reported: 2017-10-18 07:41 EDT by Martin Prpič
Modified: 2017-10-30 01:48 EDT (History)
28 users (show)

See Also:
Fixed In Version: chromium-browser 62.0.3202.62
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-10-30 01:48:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2997 normal SHIPPED_LIVE Important: chromium-browser security update 2017-10-20 08:39:11 EDT

  None (edit)
Description Martin Prpič 2017-10-18 07:41:37 EDT 
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 07:44:31 EDT 
Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1503551]
Comment 4 errata-xmlrpc 2017-10-20 04:41:00 EDT 
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 01:39:13 EDT 
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)
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.