libxslt before 9.3.3 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors, a different vulnerability than CVE-2016-4607, CVE-2016-4608, CVE-2016-4610, and CVE-2016-4612. Reference: https://seclists.org/oss-sec/2017/q2/385
Created libxslt tracking bugs for this issue: Affects: fedora-all [bug 1714986] Created mingw-libxslt tracking bugs for this issue: Affects: fedora-all [bug 1714987]
Upstream commit for this issue: https://git.gnome.org/browse/libxslt/commit/?id=8b90c9a699e0eaa98bbeec63a473ddc73aaa238c
There's a bug on libxsl before version 1.1.29 where a crafted xsl stylesheet and XML document lead to an out of band read at xmlGetLineNoInternal() from libxml2. The error happens due to improper input validation on libxslt's function exsltSaxonLineNumberFunction() when it tries to retrieve the line number for a namespace node, this bug can be leveraged to cause DoS as the out of band read will cause segmentation fault error.
Statement: Red Hat OpenStack will consume fixes from the base Red Hat Enterprise Linux Operating System. Therefore the package provided by Red Hat OpenStack has been marked as will not fix. This issue affects the version of libxslt as shipped with Red Hat Enterprise Linux 5, 6 and 7 and was rated as having Moderated security impact by the Red Hat Product Security. An eventual update for Red Hat Enterprise Linux 7 may address this issue. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.