Xmlsoft Libxslt vulnerabilities, page 2
25 vulnerabilities
Known vulnerabilities in Xmlsoft Libxslt, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2019-13118alpinelibxslt+28
EPSS score5.05%
In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data.CVE-2019-13117alpinelibxslt+9EPSS score6.29%
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.CVE-2019-11068alpinelibxslt+40EPSS score5.23%
libxslt through 1.1.33 allows bypass of a protection mechanism because callers of xsltCheckRead and xsltCheckWrite permit access even upon receiving a -1 error code. xsltCheckRead can return -1 for a crafted URL that is not actually invalid and is subsequently loaded.CVE-2019-18197alpinelibxslt+23EPSS score4.36%
In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds check could fail and memory outside a buffer could be written to, or uninitialized data could be disclosed.CVE-2019-5815debianchromium+6EPSS score1.82%
Type confusion in xsltNumberFormatGetMultipleLevel prior to libxslt 1.1.33 could allow attackers to potentially exploit heap corruption via crafted XML data.