CVE-2019-13117
libxslt: an xsl number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers
Severity
LowRed Hat Product Security
CVSS 3.1
Review impact separately from score.
Published · June 30, 2019
Updated · May 29, 2026
Description
In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This could allow an attacker to discern whether a byte on the stack contains the characters A, a, I, i, or 0, or any other character.
Statement
RH ProdSec scores this vulnerability as "Low" due to complex prerequisites for successful exploitation.
-
The attacker must be able to supply an XSLT file to a system that automatically processes it using libxslt.
-
An xsl:number element must be present with a malformed format string designed to cause an uninitialized read in xsltNumberFormatInsertNumbers.
-
While a successful exploitation will force libxslt to process memory content as if it were a format string, the attacker cannot directly control memory contents but can observe differences in output to infer values.
-
This issue affects the version of libxslt as shipped with Red Hat Gluster Storage 3, as it includes the affected code which allows uninitialized read.
-
Red Hat OpenStack Platform versions 9, 10, 13, & 14 are marked WONTFIX as they will inherit fixes from the underlying RHEL layer.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.
Mitigation
No mitigation is specified in collected source.
CVSS / CWE
CVSS 3.1 · 5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CWE-134 · Use of Externally-Controlled Format String