Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1388777 - (CVE-2016-4738) CVE-2016-4738 libxslt: Heap overread due to an empty decimal-separator
CVE-2016-4738 libxslt: Heap overread due to an empty decimal-separator
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161012,repor...
: Security
Depends On: 1388780 1388781 1388779
Blocks: 1388784
  Show dependency treegraph
 
Reported: 2016-10-26 03:50 EDT by Andrej Nemec
Modified: 2018-02-09 10:17 EST (History)
34 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-09 08:41:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2016-10-26 03:50:45 EDT
A heap overread vulnerability was found in xsltFormatNumberConversion function in libxslt. An empty decimal-separator could cause a heap overread. This can be exploited to leak a couple of bytes after the buffer that holds the pattern string.

Upstream patch:

https://git.gnome.org/browse/libxslt/commit/?id=eb1030de31165b68487f288308f9d1810fed6880
Comment 1 Andrej Nemec 2016-10-26 03:56:24 EDT
Created libxslt tracking bugs for this issue:

Affects: fedora-all [bug 1388779]
Comment 2 Andrej Nemec 2016-10-26 03:56:44 EDT
Created mingw-libxslt tracking bugs for this issue:

Affects: fedora-all [bug 1388780]
Affects: epel-7 [bug 1388781]
Comment 4 Huzaifa S. Sidhpurwala 2016-10-31 04:50:02 EDT
This issue was initially filed as chromium bug at:

https://bugs.chromium.org/p/chromium/issues/detail?id=619006

Note You need to log in before you can comment on or make changes to this bug.