Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1452549 - (CVE-2017-9048) CVE-2017-9048 libxml2: Stack-based buffer overflow in function xmlSnprintfElementContent
CVE-2017-9048 libxml2: Stack-based buffer overflow in function xmlSnprintfEle...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20170515,reported=2...
: Security
Depends On: 1548942 1452550 1452551
Blocks: 1452558
  Show dependency treegraph
 
Reported: 2017-05-19 03:54 EDT by Andrej Nemec
Modified: 2018-04-24 08:42 EDT (History)
19 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-26 00:10:17 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 2017-05-19 03:54:30 EDT
libxml2 is vulnerable to a stack-based buffer overflow. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. At the end of the routine, the function may strcat two more characters without checking whether the current strlen(buf) + 2 < size. This vulnerability causes programs that use libxml2 to crash. 

References:

http://seclists.org/oss-sec/2017/q2/258
Comment 1 Andrej Nemec 2017-05-19 03:55:03 EDT
Created libxml2 tracking bugs for this issue:

Affects: fedora-all [bug 1452550]


Created mingw-libxml2 tracking bugs for this issue:

Affects: fedora-all [bug 1452551]
Comment 3 Doran Moppert 2018-02-25 23:48:53 EST
Statement:

This vulnerability exists in the DTD validation functionality of libxml2.  Applications that do not attempt to validate untrusted documents are not impacted.

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