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
Created chromium tracking bugs for this issue: Affects: fedora-all [bug 1503551]
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
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)
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.