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.
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14471
https://gitlab.gnome.org/GNOME/libxslt/commit/c5eb6cf3aba0af048596106ed839b4ae17ecbcb1
https://oss-fuzz.com/testcase-detail/5631739747106816
https://lists.debian.org/debian-lts-announce/2019/07/msg00020.html
https://security.netapp.com/advisory/ntap-20190806-0004/
https://usn.ubuntu.com/4164-1/
http://www.openwall.com/lists/oss-security/2019/11/17/2
https://www.oracle.com/security-alerts/cpujan2020.html
https://security.netapp.com/advisory/ntap-20200122-0003/
http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00062.html
https://lists.apache.org/thread.html/[email protected]%3Cissues.bookkeeper.apache.org%3E
https://lists.apache.org/thread.html/[email protected]%3Cissues.bookkeeper.apache.org%3E
Source: MITRE
Published: 2019-07-01
Updated: 2021-06-29
Type: CWE-908
Base Score: 5
Vector: AV:N/AC:L/Au:N/C:P/I:N/A:N
Impact Score: 2.9
Exploitability Score: 10
Severity: MEDIUM
Base Score: 7.5
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Impact Score: 3.6
Exploitability Score: 3.9
Severity: HIGH