Overview 7 matches · 2 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5
7matches
2in Waratek scope28.6%
1protected14.3%
0exploited0.0%
0CISA KEV0.0%
1public PoC14.3%
1EPSS ≥ 0.514.3%
Protected by Waratek
1
14.3%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
14.3%
Outside Waratek scope
1
14.3%
Not applicable
4
57.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
14.3%
partly blocked
0
0.0%
not blocked
6
85.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
1
14.3%
Forecast only
0
0.0%
No public exploit
6
85.7%
split by
peak 3 / quarter
Q2 171
Outside Waratek scope1
High1
not blocked1
No public exploit1
Q3 170
Q4 170
Q1 180
Q2 180
Q3 180
Q4 180
Q1 190
Q2 190
Q3 190
Q4 193
Protected by Waratek1
Not applicable2
Critical1
High1
Medium1
blocked by ARMR today1
not blocked2
Proof of concept only1
No public exploit2
Q1 200
Q2 200
Q3 200
Q4 200
Q1 211
Not applicable1
High1
not blocked1
No public exploit1
Q2 211
Not applicable1
High1
not blocked1
No public exploit1
Q3 210
Q4 210
Q1 220
Q2 220
Q3 220
Q4 221
No exploit published1
Medium1
not blocked1
No public exploit1
Q2 17Q4 17Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21Q4 21Q2 22Q4 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-32531 | Medium | 2022-12-15 | No exploit published | No public exploit | The Apache Bookkeeper Java Client (before 4.14.6 and also 4.15.0) does not close the connection to the bookkeeper server when TLS hostname verification fails. This leaves the bookkeeper client vulnerable to a man in the middle attack. The problem affects BookKeeper client prior to versions 4.14.6 and 4.15.1. |
| CVE-2020-23922 | High | 2021-04-21 | Not applicable | No public exploit | An issue was discovered in giflib through 5.1.4. DumpScreen2RGB in gif2rgb.c has a heap-based buffer over-read. |
| CVE-2020-36230 | High | 2021-01-26 | Not applicable | No public exploit | A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service. |
| CVE-2019-19924 | Medium | 2019-12-24 | Not applicable | No public exploit | SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling. |
| CVE-2019-17571 | Critical | 2019-12-20 | Protected by Waratek | Proof of concept only | Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17. |
| CVE-2019-19906 | High | 2019-12-19 | Not applicable | No public exploit | cyrus-sasl (aka Cyrus SASL) 2.1.27 has an out-of-bounds write leading to unauthenticated remote denial-of-service in OpenLDAP via a malformed LDAP packet. The OpenLDAP crash is ultimately caused by an off-by-one error in _sasl_add_string in common.c in cyrus-sasl. |
| CVE-2017-6891 | High | 2017-05-22 | Outside Waratek scope | No public exploit | Two errors in the "asn1_find_node()" function (lib/parser_aux.c) within GnuTLS libtasn1 version 4.10 can be exploited to cause a stacked-based buffer overflow by tricking a user into processing a specially crafted assignments file via the e.g. asn1Coding utility. |