Owasp CVEs with no public exploit
10 CVEs, 4 protected by Waratek
Overview 10 matches · 4 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
4
40.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
6
60.0%
blocked by ARMR today
4
40.0%
partly blocked
0
0.0%
not blocked
6
60.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
10
100.0%
split by
peak 5 / year
20132
Protected by Waratek1
No exploit published1
Medium1
Low1
blocked by ARMR today1
not blocked1
No public exploit2
20140
20150
20160
20170
20181
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
20190
20201
No exploit published1
Medium1
not blocked1
No public exploit1
20215
Protected by Waratek2
No exploit published3
Critical2
High2
Medium1
blocked by ARMR today2
not blocked3
No public exploit5
20221
No exploit published1
Medium1
not blocked1
No public exploit1
2013201420152016201720182019202020212022
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-27820 | Medium | 2022-03-24 | No exploit published | No public exploit | OWASP Zed Attack Proxy (ZAP) through w2022-03-21 does not verify the TLS certificate chain of an HTTPS server. |
| CVE-2021-42575 | Critical | 2021-10-18 | Protected by Waratek | No public exploit | The OWASP Java HTML Sanitizer before 20211018.1 does not properly enforce policies associated with the SELECT, STYLE, and OPTION elements. |
| CVE-2021-28490 | High | 2021-08-19 | No exploit published | No public exploit | In OWASP CSRFGuard through 3.1.0, CSRF can occur because the CSRF cookie may be retrieved by using only a session token. |
| CVE-2010-3300 | Medium | 2021-06-22 | No exploit published | No public exploit | It was found that all OWASP ESAPI for Java up to version 2.0 RC2 are vulnerable to padding oracle attacks. |
| CVE-2021-23900 | High | 2021-01-13 | No exploit published | No public exploit | OWASP json-sanitizer before 1.2.2 can output invalid JSON or throw an undeclared exception for crafted input. This may lead to denial of service if the application is not prepared to handle these situations. |
| CVE-2021-23899 | Critical | 2021-01-13 | Protected by Waratek | No public exploit | OWASP json-sanitizer before 1.2.2 may emit closing SCRIPT tags and CDATA section delimiters for crafted input. This allows an attacker to inject arbitrary HTML or XML into embedding documents. |
| CVE-2020-13973 | Medium | 2020-06-09 | No exploit published | No public exploit | OWASP json-sanitizer before 1.2.1 allows XSS. An attacker who controls a substring of the input JSON, and controls another substring adjacent to a SCRIPT element in which the output is embedded as JavaScript, may be able to confuse the HTML parser as to where the SCRIPT element ends, and cause non-script content to be interpreted as JavaScript. |
| CVE-2018-12036 | High | 2018-06-07 | Protected by Waratek | No public exploit | OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames. |
| CVE-2013-5960 | Medium | 2013-09-30 | No exploit published | No public exploit | The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0.1 does not properly resist tampering with serialized ciphertext, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against the intended cipher mode in a non-default configuration, a different vulnerability than CVE-2013-5679. |
| CVE-2013-5679 | Low | 2013-09-30 | Protected by Waratek | No public exploit | The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0 does not properly resist tampering with serialized ciphertext, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against authenticity in the default configuration, involving a null MAC and a zero MAC length. |