Overview 143 matches · 0 in Waratek scope · 0 protected · 2 exploited · 0 CISA KEV · 8 public PoC · 0 EPSS ≥ 0.5
143matches
0in Waratek scope0.0%
0protected0.0%
2exploited1.4%
0CISA KEV0.0%
8public PoC5.6%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
9
6.3%
Not applicable
134
93.7%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
143
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 27 / year
20031
Not applicable1
Medium1
not blocked1
No public exploit1
20041
Not applicable1
High1
not blocked1
Working exploit published1
20051
Not applicable1
High1
not blocked1
Working exploit published1
20060
20070
20086
Not applicable6
High4
Medium2
not blocked6
Working exploit published3
No public exploit3
20092
Not applicable2
Medium2
not blocked2
No public exploit2
20102
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20112
Not applicable2
High1
Medium1
not blocked2
Working exploit published1
No public exploit1
20125
Not applicable5
Medium5
not blocked5
No public exploit5
20135
Not applicable5
High1
Medium4
not blocked5
No public exploit5
20142
Not applicable2
Medium2
not blocked2
No public exploit2
201513
Not applicable13
High1
Medium11
Low1
not blocked13
No public exploit13
201627
Not applicable27
Critical7
High13
Medium7
not blocked27
Working exploit published2
Proof of concept only1
No public exploit24
201711
Not applicable11
Critical2
High7
Medium2
not blocked11
Proof of concept only1
No public exploit10
201811
Not applicable11
Critical2
High3
Medium6
not blocked11
No public exploit11
20196
Outside Waratek scope1
Not applicable5
Critical1
High3
Medium2
not blocked6
No public exploit6
20203
Outside Waratek scope3
High2
Medium1
not blocked3
Proof of concept only1
No public exploit2
20216
Not applicable6
High4
Medium2
not blocked6
No public exploit6
20225
Not applicable5
High3
Medium2
not blocked5
Exploited2
No public exploit3
20234
Not applicable4
Medium4
not blocked4
Proof of concept only1
No public exploit3
20243
Outside Waratek scope1
Not applicable2
Critical1
High2
not blocked3
Proof of concept only1
No public exploit2
202513
Outside Waratek scope4
Not applicable9
Critical1
High9
Medium1
Low2
not blocked13
Proof of concept only4
No public exploit9
202614
Not applicable14
High8
Medium2
Low4
not blocked14
No public exploit14
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2015-8710 | Critical | 2016-04-11 | Not applicable | No public exploit | The htmlParseComment function in HTMLparser.c in libxml2 allows attackers to obtain sensitive information, cause a denial of service (out-of-bounds heap memory access and application crash), or possibly have unspecified other impact via an unclosed HTML comment. |
| CVE-2016-1762 | High | 2016-03-24 | Not applicable | No public exploit | The xmlNextChar function in libxml2 before 2.9.4 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted XML document. |
| CVE-2016-2073 | Medium | 2016-02-12 | Not applicable | No public exploit | The htmlParseNameComplex function in HTMLparser.c in libxml2 allows attackers to cause a denial of service (out-of-bounds read) via a crafted XML document. |
| CVE-2015-8317 | Medium | 2015-12-15 | Not applicable | No public exploit | The xmlParseXMLDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive information via an (1) unterminated encoding value or (2) incomplete XML declaration in XML data, which triggers an out-of-bounds heap read. |
| CVE-2015-8242 | Medium | 2015-12-15 | Not applicable | No public exploit | The xmlSAX2TextNode function in SAX2.c in the push interface in the HTML parser in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service (stack-based buffer over-read and application crash) or obtain sensitive information via crafted XML data. |
| CVE-2015-8241 | Medium | 2015-12-15 | Not applicable | No public exploit | The xmlNextChar function in libxml2 2.9.2 does not properly check the state, which allows context-dependent attackers to cause a denial of service (heap-based buffer over-read and application crash) or obtain sensitive information via crafted XML data. |
| CVE-2015-7500 | Medium | 2015-12-15 | Not applicable | No public exploit | The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service (out-of-bounds heap read) via unspecified vectors related to incorrect entities boundaries and start tags. |
| CVE-2015-7499 | Medium | 2015-12-15 | Not applicable | No public exploit | Heap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive process memory information via unspecified vectors. |
| CVE-2015-7498 | Medium | 2015-12-15 | Not applicable | No public exploit | Heap-based buffer overflow in the xmlParseXmlDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service via unspecified vectors related to extracting errors after an encoding conversion failure. |
| CVE-2015-7497 | Medium | 2015-12-15 | Not applicable | No public exploit | Heap-based buffer overflow in the xmlDictComputeFastQKey function in dict.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service via unspecified vectors. |
| CVE-2015-5312 | High | 2015-12-15 | Not applicable | No public exploit | The xmlStringLenDecodeEntities function in parser.c in libxml2 before 2.9.3 does not properly prevent entity expansion, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted XML data, a different vulnerability than CVE-2014-3660. |
| CVE-2015-8035 | Low | 2015-11-18 | Not applicable | No public exploit | The xz_decomp function in xzlib.c in libxml2 2.9.1 does not properly detect compression errors, which allows context-dependent attackers to cause a denial of service (process hang) via crafted XML data. |
| CVE-2015-7942 | Medium | 2015-11-18 | Not applicable | No public exploit | The xmlParseConditionalSections function in parser.c in libxml2 does not properly skip intermediary entities when it stops parsing invalid input, which allows context-dependent attackers to cause a denial of service (out-of-bounds read and crash) via crafted XML data, a different vulnerability than CVE-2015-7941. |
| CVE-2015-7941 | Medium | 2015-11-18 | Not applicable | No public exploit | libxml2 2.9.2 does not properly stop parsing invalid input, which allows context-dependent attackers to cause a denial of service (out-of-bounds read and libxml2 crash) via crafted XML data to the (1) xmlParseEntityDecl or (2) xmlParseConditionalSections function in parser.c, as demonstrated by non-terminated entities. |
| CVE-2015-7995 | Medium | 2015-11-17 | Not applicable | No public exploit | 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. |
| CVE-2015-1819 | Medium | 2015-08-14 | Not applicable | No public exploit | The xmlreader in libxml allows remote attackers to cause a denial of service (memory consumption) via crafted XML data, related to an XML Entity Expansion (XEE) attack. |
| CVE-2014-3660 | Medium | 2014-11-04 | Not applicable | No public exploit | parser.c in libxml2 before 2.9.2 does not properly prevent entity expansion even when entity substitution has been disabled, which allows context-dependent attackers to cause a denial of service (CPU consumption) via a crafted XML document containing a large number of nested entity references, a variant of the "billion laughs" attack. |
| CVE-2013-0339 | Medium | 2014-01-21 | Not applicable | No public exploit | libxml2 through 2.9.1 does not properly handle external entities expansion unless an application developer uses the xmlSAX2ResolveEntity or xmlSetExternalEntityLoader function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because libxml2 already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed and each affected application would need its own CVE. |
| CVE-2013-4520 | Medium | 2013-12-14 | Not applicable | No public exploit | xslt.c in libxslt before 1.1.25 allows context-dependent attackers to cause a denial of service (crash) via a stylesheet that embeds a DTD, which causes a structure to be accessed as a different type. NOTE: this issue is due to an incomplete fix for CVE-2012-2825. |
| CVE-2013-2877 | Medium | 2013-07-10 | Not applicable | No public exploit | parser.c in libxml2 before 2.9.0, as used in Google Chrome before 28.0.1500.71 and other products, allows remote attackers to cause a denial of service (out-of-bounds read) via a document that ends abruptly, related to the lack of certain checks for the XML_PARSER_EOF state. |
| CVE-2013-1969 | High | 2013-04-25 | Not applicable | No public exploit | Multiple use-after-free vulnerabilities in libxml2 2.9.0 and possibly other versions might allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via vectors related to the (1) htmlParseChunk and (2) xmldecl_done functions, as demonstrated by a buffer overflow in the xmlBufGetInputBase function. |
| CVE-2013-0338 | Medium | 2013-04-25 | Not applicable | No public exploit | libxml2 2.9.0 and earlier allows context-dependent attackers to cause a denial of service (CPU and memory consumption) via an XML file containing an entity declaration with long replacement text and many references to this entity, aka "internal entity expansion" with linear complexity. |
| CVE-2012-6139 | Medium | 2013-04-12 | Not applicable | No public exploit | 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. |
| CVE-2012-0841 | Medium | 2012-12-21 | Not applicable | No public exploit | libxml2 before 2.8.0 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted XML data. |
| CVE-2012-5134 | Medium | 2012-11-28 | Not applicable | No public exploit | Heap-based buffer underflow in the xmlParseAttValueComplex function in parser.c in libxml2 2.9.0 and earlier, as used in Google Chrome before 23.0.1271.91 and other products, allows remote attackers to cause a denial of service or possibly execute arbitrary code via crafted entities in an XML document. |
| CVE-2012-2871 | Medium | 2012-08-31 | Not applicable | No public exploit | libxml2 2.9.0-rc1 and earlier, as used in Google Chrome before 21.0.1180.89, does not properly support a cast of an unspecified variable during handling of XSL transforms, which allows remote attackers to cause a denial of service or possibly have unknown other impact via a crafted document, related to the _xmlNs data structure in include/libxml/tree.h. |
| CVE-2012-2870 | Medium | 2012-08-31 | Not applicable | No public exploit | libxslt 1.1.26 and earlier, as used in Google Chrome before 21.0.1180.89, does not properly manage memory, which might allow remote attackers to cause a denial of service (application crash) via a crafted XSLT expression that is not properly identified during XPath navigation, related to (1) the xsltCompileLocationPathPattern function in libxslt/pattern.c and (2) the xsltGenerateIdFunction function in libxslt/functions.c. |
| CVE-2011-3970 | Medium | 2012-02-09 | Not applicable | No public exploit | libxslt, as used in Google Chrome before 17.0.963.46, allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors. |
| CVE-2011-1944 | High | 2011-09-02 | Not applicable | Working exploit published | Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. |
| CVE-2011-1202 | Medium | 2011-03-11 | Not applicable | No public exploit | The xsltGenerateIdFunction function in functions.c in libxslt 1.1.26 and earlier, as used in Google Chrome before 10.0.648.127 and other products, allows remote attackers to obtain potentially sensitive information about heap memory addresses via an XML document containing a call to the XSLT generate-id XPath function. |
| CVE-2010-4494 | High | 2010-12-07 | Not applicable | No public exploit | Double free vulnerability in libxml2 2.7.8 and other versions, as used in Google Chrome before 8.0.552.215 and other products, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to XPath handling. |
| CVE-2010-4008 | Medium | 2010-11-17 | Not applicable | No public exploit | libxml2 before 2.7.8, as used in Google Chrome before 7.0.517.44, Apple Safari 5.0.2 and earlier, and other products, reads from invalid memory locations during processing of malformed XPath expressions, which allows context-dependent attackers to cause a denial of service (application crash) via a crafted XML document. |
| CVE-2009-2416 | Medium | 2009-08-11 | Not applicable | No public exploit | Multiple use-after-free vulnerabilities in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allow context-dependent attackers to cause a denial of service (application crash) via crafted (1) Notation or (2) Enumeration attribute types in an XML file, as demonstrated by the Codenomicon XML fuzzing framework. |
| CVE-2009-2414 | Medium | 2009-08-11 | Not applicable | No public exploit | Stack consumption vulnerability in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allows context-dependent attackers to cause a denial of service (application crash) via a large depth of element declarations in a DTD, related to a function recursion, as demonstrated by the Codenomicon XML fuzzing framework. |
| CVE-2008-4226 | High | 2008-11-25 | Not applicable | No public exploit | Integer overflow in the xmlSAX2Characters function in libxml2 2.7.2 allows context-dependent attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via a large XML document. |
| CVE-2008-4225 | High | 2008-11-25 | Not applicable | No public exploit | Integer overflow in the xmlBufferResize function in libxml2 2.7.2 allows context-dependent attackers to cause a denial of service (infinite loop) via a large XML document. |
| CVE-2008-4409 | Medium | 2008-10-03 | Not applicable | Working exploit published | libxml2 2.7.0 and 2.7.1 does not properly handle "predefined entities definitions" in entities, which allows context-dependent attackers to cause a denial of service (memory consumption and application crash), as demonstrated by use of xmllint on a certain XML document, a different vulnerability than CVE-2003-1564 and CVE-2008-3281. |
| CVE-2008-3529 | High | 2008-09-12 | Not applicable | Working exploit published | Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers to cause a denial of service (crash) or execute arbitrary code via a long XML entity name. |
| CVE-2008-3281 | Medium | 2008-08-27 | Not applicable | No public exploit | libxml2 2.6.32 and earlier does not properly detect recursion during entity expansion in an attribute value, which allows context-dependent attackers to cause a denial of service (memory and CPU consumption) via a crafted XML document. |
| CVE-2008-2935 | High | 2008-08-01 | Not applicable | Working exploit published | Multiple heap-based buffer overflows in the rc4 (1) encryption (aka exsltCryptoRc4EncryptFunction) and (2) decryption (aka exsltCryptoRc4DecryptFunction) functions in crypto.c in libexslt in libxslt 1.1.8 through 1.1.24 allow context-dependent attackers to execute arbitrary code via an XML file containing a long string as "an argument in the XSL input." |
| CVE-2004-0989 | High | 2005-03-01 | Not applicable | Working exploit published | Multiple buffer overflows in libXML 2.6.12 and 2.6.13 (libxml2), and possibly other versions, may allow remote attackers to execute arbitrary code via (1) a long FTP URL that is not properly handled by the xmlNanoFTPScanURL function, (2) a long proxy URL containing FTP data that is not properly handled by the xmlNanoFTPScanProxy function, and other overflows related to manipulation of DNS length values, including (3) xmlNanoFTPConnect, (4) xmlNanoHTTPConnectHost, and (5) xmlNanoHTTPConnectHost. |
| CVE-2004-0110 | High | 2004-03-15 | Not applicable | Working exploit published | Buffer overflow in the (1) nanohttp or (2) nanoftp modules in XMLSoft Libxml 2 (Libxml2) 2.6.0 through 2.6.5 allow remote attackers to execute arbitrary code via a long URL. |
| CVE-2003-1564 | Medium | 2003-12-31 | Not applicable | No public exploit | libxml2, possibly before 2.5.0, does not properly detect recursion during entity expansion, which allows context-dependent attackers to cause a denial of service (memory and CPU consumption) via a crafted XML document containing a large number of nested entity references, aka the "billion laughs attack." |