Lucene search

K
XmlsoftLibxslt

5 matches found

CVE
CVE
added 2019/07/01 2:15 a.m.297 views

CVE-2019-13118

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.

5.3CVSS6.1AI score0.01193EPSS
CVE
CVE
added 2019/07/01 2:15 a.m.249 views

CVE-2019-13117

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.

5.3CVSS5.9AI score0.05184EPSS
CVE
CVE
added 2015/11/17 3:59 p.m.105 views

CVE-2015-7995

The xsltStylePreCompute function in preproc.c in libxslt 1.1.28 does not check if the parent node is an element, which allows attackers to cause a denial of service via a crafted XML file, related to a "type confusion" issue.

5CVSS6.1AI score0.03037EPSS
CVE
CVE
added 2017/04/05 9:59 p.m.77 views

CVE-2015-9019

In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.

5.3CVSS6.3AI score0.00984EPSS
CVE
CVE
added 2013/04/12 10:55 p.m.72 views

CVE-2012-6139

libxslt before 1.1.28 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via an (1) empty match attribute in a XSL key to the xsltAddKey function in keys.c or (2) uninitialized variable to the xsltDocumentFunction function in functions.c.

5CVSS8.9AI score0.04603EPSS