Summary
This update for libxml2 fixes the following issues:
* CVE-2016-4658: use-after-free error could lead to crash [bsc#1005544]
* Fix NULL dereference in xpointer.c when in recovery mode [bsc#1014873]
* CVE-2016-9597: An XML document with many opening tags could have caused a overflow of the stack not detected by the recursion limits, allowing for DoS (bsc#1017497).
For CVE-2016-9318 we decided not to ship a fix since it can break existing setups. Please take appropriate actions if you parse untrusted XML files
and use the new -noxxe flag if possible (bnc#1010675, bnc#1013930).
Fixed packages 9
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 12 SP2 Linux Enterprise Desktop 12 SP2 | libxml2 | 2.9.4-33.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Desktop 12 SP2 | python-libxml2 | 2.9.4-33.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Server 12 SP2 | libxml2 | 2.9.4-33.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Server 12 SP2 | python-libxml2 | 2.9.4-33.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Server for Raspberry Pi 12 SP2 | libxml2 | 2.9.4-33.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Server for Raspberry Pi 12 SP2 | python-libxml2 | 2.9.4-33.1 |
| SUSE · SLES for SAP 12 SP2 Linux Enterprise Server for SAP Applications 12 SP2 | libxml2 | 2.9.4-33.1 |
| SUSE · SLES for SAP 12 SP2 Linux Enterprise Server for SAP Applications 12 SP2 | python-libxml2 | 2.9.4-33.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Software Development Kit 12 SP2 | libxml2 | 2.9.4-33.1 |
Vulnerabilities 3
-
Critical 9.8
Nokogiri does not forbid namespace nodes in XPointer ranges
xpointer.c in libxml2 before 2.9.5 (as used in Apple iOS before 10, OS X before 10.12, tvOS before 10, and watchOS before 3, and other products) does not forbid namespace nodes in XPointer ranges, which allows remote attackers to execute arbitrary code or cau…
-
Medium 5.5
libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag directly indi…
-
Unscored —
It was found that Red Hat JBoss Core Services erratum RHSA-2016:2957 for CVE-2016-3705 did not actually include the fix…
References
-
report
https://bugzilla.suse.com/1005544
-
report
https://bugzilla.suse.com/1010675
-
report
https://bugzilla.suse.com/1013930
-
report
https://bugzilla.suse.com/1014873
-
report
https://bugzilla.suse.com/1017497
-
web
https://www.suse.com/security/cve/CVE-2016-4658
-
web
https://www.suse.com/security/cve/CVE-2016-9318
-
web
https://www.suse.com/security/cve/CVE-2016-9597