Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1619875 - (CVE-2018-14567) CVE-2018-14567 libxml2: Infinite loop when --with-lzma is used allows for denial of service via crafted XML file
CVE-2018-14567 libxml2: Infinite loop when --with-lzma is used allows for den...
Status: NEW
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=20180403,reported=2...
: Reopened, Security
Depends On: 1619879 1619880 1619881 1622715 1619878
Blocks: 1619882
  Show dependency treegraph
 
Reported: 2018-08-21 21:47 EDT by Sam Fowler
Modified: 2018-09-24 19:45 EDT (History)
28 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-09-02 11:53:28 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)

  None (edit)
Description Sam Fowler 2018-08-21 21:47:36 EDT
libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035 and CVE-2018-9251.


Upstream Patch:

https://gitlab.gnome.org/GNOME/libxml2/commit/2240fbf5912054af025fb6e01e26375100275e74
Comment 1 Sam Fowler 2018-08-21 21:50:18 EDT
Created libxml2 tracking bugs for this issue:

Affects: fedora-all [bug 1619878]


Created mingw-libxml2 tracking bugs for this issue:

Affects: epel-7 [bug 1619880]
Affects: fedora-all [bug 1619879]
Comment 4 Scott Gayou 2018-08-27 15:38:30 EDT
RHEL5/6 use a libxml2 version released before it had LZMA support.
Comment 7 Doran Moppert 2018-08-31 01:28:22 EDT
Statement:

Red Hat Product Security has rated this flaw as having Low impact. A future update may address this issue.

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