Overview 27 matches · 3 in Waratek scope · 1 protected · 1 exploited · 1 CISA KEV · 3 public PoC · 1 EPSS ≥ 0.5
27matches
3in Waratek scope11.1%
1protected3.7%
1exploited3.7%
1CISA KEV3.7%
3public PoC11.1%
1EPSS ≥ 0.53.7%
Protected by Waratek
1
3.7%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
2
7.4%
Outside Waratek scope
12
44.4%
Not applicable
12
44.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
3.7%
partly blocked
0
0.0%
not blocked
26
96.3%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
3.7%
Working exploit published
0
0.0%
Proof of concept only
8
29.6%
Forecast only
0
0.0%
No public exploit
18
66.7%
split by
peak 5 / quarter
Q2 191
Outside Waratek scope1
High1
not blocked1
No public exploit1
Q3 190
Q4 190
Q1 200
Q2 201
Outside Waratek scope1
Medium1
not blocked1
No public exploit1
Q3 200
Q4 203
Outside Waratek scope3
High2
Low1
not blocked3
No public exploit3
Q1 210
Q2 210
Q3 210
Q4 211
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Q1 221
Not applicable1
Medium1
not blocked1
No public exploit1
Q2 224
Not applicable4
High2
Medium2
not blocked4
Proof of concept only3
No public exploit1
Q3 223
No exploit published2
Not applicable1
High2
Low1
not blocked3
Proof of concept only1
No public exploit2
Q4 220
Q1 230
Q2 230
Q3 235
Outside Waratek scope1
Not applicable4
Critical4
High1
not blocked5
No public exploit5
Q4 231
Outside Waratek scope1
High1
not blocked1
Proof of concept only1
Q1 240
Q2 242
Outside Waratek scope2
Critical1
High1
not blocked2
No public exploit2
Q3 240
Q4 242
Outside Waratek scope2
Critical1
Medium1
not blocked2
Proof of concept only1
No public exploit1
Q1 253
Outside Waratek scope1
Not applicable2
High1
Medium1
Low1
not blocked3
Proof of concept only2
No public exploit1
Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-0725 | High | 2025-02-05 | Not applicable | Proof of concept only | When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer overflow. |
| CVE-2025-0167 | Low | 2025-02-05 | Not applicable | Proof of concept only | When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a `default` entry that omits both login and password. A rare circumstance. |
| CVE-2024-13176 | Medium | 2025-01-20 | Outside Waratek scope | No public exploit | Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue. |
| CVE-2024-40896 | Critical | 2024-12-23 | Outside Waratek scope | No public exploit | In libxml2 2.11 before 2.11.9, 2.12 before 2.12.9, and 2.13 before 2.13.3, the SAX parser can produce events for external entities even if custom SAX handlers try to override entity content (by setting "checked"). This makes classic XXE attacks possible. |
| CVE-2024-50602 | Medium | 2024-10-27 | Outside Waratek scope | Proof of concept only | An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser. |
| CVE-2024-36958 | Critical | 2024-05-30 | Outside Waratek scope | No public exploit | In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix nfsd4_encode_fattr4() crasher Ensure that args.acl is initialized early. It is used in an unconditional call to kfree() on the way out of nfsd4_encode_fattr4(). |
| CVE-2024-33602 | High | 2024-05-06 | Outside Waratek scope | No public exploit | nscd: netgroup cache assumes NSS callback uses in-buffer strings The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary. |
| CVE-2023-5178 | High | 2023-11-01 | Outside Waratek scope | Proof of concept only | A use-after-free vulnerability was found in drivers/nvme/target/tcp.c` in `nvmet_tcp_free_crypto` due to a logical bug in the NVMe/TCP subsystem in the Linux kernel. This issue may allow a malicious user to cause a use-after-free and double-free problem, which may permit remote code execution or lead to local privilege escalation. |
| CVE-2023-37920 | Critical | 2023-07-25 | Outside Waratek scope | No public exploit | Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi prior to version 2023.07.22 recognizes "e-Tugra" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from "e-Tugra" from the root store. |
| CVE-2023-32257 | High | 2023-07-24 | Not applicable | No public exploit | A flaw was found in the Linux kernel's ksmbd, a high-performance in-kernel SMB server. The specific flaw exists within the processing of SMB2_SESSION_SETUP and SMB2_LOGOFF commands. The issue results from the lack of proper locking when performing operations on an object. An attacker can leverage this vulnerability to execute code in the context of the kernel. |
| CVE-2023-38432 | Critical | 2023-07-18 | Not applicable | No public exploit | An issue was discovered in the Linux kernel before 6.3.10. fs/smb/server/smb2misc.c in ksmbd does not validate the relationship between the command payload size and the RFC1002 length specification, leading to an out-of-bounds read. |
| CVE-2023-38428 | Critical | 2023-07-18 | Not applicable | No public exploit | An issue was discovered in the Linux kernel before 6.3.4. fs/ksmbd/smb2pdu.c in ksmbd does not properly check the UserName value because it does not consider the address of security buffer, leading to an out-of-bounds read. |
| CVE-2023-38426 | Critical | 2023-07-18 | Not applicable | No public exploit | An issue was discovered in the Linux kernel before 6.3.4. ksmbd has an out-of-bounds read in smb2_find_context_vals when create_context's name_len is larger than the tag length. |
| CVE-2022-36946 | High | 2022-07-27 | Not applicable | Proof of concept only | nfqnl_mangle in net/netfilter/nfnetlink_queue.c in the Linux kernel through 5.18.14 allows remote attackers to cause a denial of service (panic) because, in the case of an nf_queue verdict with a one-byte nfta_payload attribute, an skb_pull can encounter a negative skb->len. |
| CVE-2022-2048 | High | 2022-07-07 | No exploit published | No public exploit | In Eclipse Jetty HTTP/2 server implementation, when encountering an invalid HTTP/2 request, the error handling has a bug that can wind up not properly cleaning up the active connections and associated resources. This can lead to a Denial of Service scenario where there are no enough resources left to process good requests. |
| CVE-2022-2047 | Low | 2022-07-07 | No exploit published | No public exploit | In Eclipse Jetty versions 9.4.0 thru 9.4.46, and 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, the parsing of the authority segment of an http scheme URI, the Jetty HttpURI class improperly detects an invalid input as a hostname. This can lead to failures in a Proxy scenario. |
| CVE-2022-27776 | Medium | 2022-06-02 | Not applicable | No public exploit | A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number. |
| CVE-2022-27775 | High | 2022-06-02 | Not applicable | Proof of concept only | An information disclosure vulnerability exists in curl 7.65.0 to 7.82.0 are vulnerable that by using an IPv6 address that was in the connection pool but with a different zone id it could reuse a connection instead. |
| CVE-2022-27774 | Medium | 2022-06-02 | Not applicable | Proof of concept only | An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers. |
| CVE-2022-22576 | High | 2022-05-26 | Not applicable | Proof of concept only | An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only). |
| CVE-2021-3772 | Medium | 2022-03-02 | Not applicable | No public exploit | A flaw was found in the Linux SCTP stack. A blind attacker may be able to kill an existing SCTP association through invalid chunks if the attacker knows the IP-addresses and port numbers being used and the attacker can send packets with spoofed IP addresses. |
| CVE-2021-44228 | Critical | 2021-12-10 | Protected by Waratek | Exploited | Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects. |
| CVE-2020-29569 | High | 2020-12-15 | Outside Waratek scope | No public exploit | An issue was discovered in the Linux kernel through 5.10.1, as used with Xen through 4.14.x. The Linux kernel PV block backend expects the kernel thread handler to reset ring->xenblkd to NULL when stopped. However, the handler may not have time to run if the frontend quickly toggles between the states connect and disconnect. As a consequence, the block backend may re-use a pointer after it was freed. A misbehaving guest can trigger a dom0 crash by continuously connecting / disconnecting a block frontend. Privilege escalation and information leaks cannot be ruled out. This only affects systems with a Linux blkback. |
| CVE-2020-29374 | Low | 2020-11-28 | Outside Waratek scope | No public exploit | An issue was discovered in the Linux kernel before 5.7.3, related to mm/gup.c and mm/huge_memory.c. The get_user_pages (aka gup) implementation, when used for a copy-on-write page, does not properly consider the semantics of read operations and therefore can grant unintended write access, aka CID-17839856fd58. |
| CVE-2020-25645 | High | 2020-10-13 | Outside Waratek scope | No public exploit | A flaw was found in the Linux kernel in versions before 5.9-rc7. Traffic between two Geneve endpoints may be unencrypted when IPsec is configured to encrypt traffic for the specific UDP port used by the GENEVE tunnel allowing anyone between the two endpoints to read the traffic unencrypted. The main threat from this vulnerability is to data confidentiality. |
| CVE-2020-12464 | Medium | 2020-04-29 | Outside Waratek scope | No public exploit | usb_sg_cancel in drivers/usb/core/message.c in the Linux kernel before 5.6.8 has a use-after-free because a transfer occurs without a reference, aka CID-056ad39ee925. |
| CVE-2018-20836 | High | 2019-05-07 | Outside Waratek scope | No public exploit | An issue was discovered in the Linux kernel before 4.20. There is a race condition in smp_task_timedout() and smp_task_done() in drivers/scsi/libsas/sas_expander.c, leading to a use-after-free. |