WaratekVRT Sign in

Medium CWE-787 CVEs

18 CVEs, 1 protected by Waratek

Reset
More filters (1)
Columns
CWE CWE-787✕
Overview 18 matches · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
18matches 1protected5.6% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 1 5.6% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 17 94.4%
Critical 0 0.0% High 0 0.0% Medium 18 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 1 5.6% partly blocked 0 0.0% not blocked 17 94.4% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 3 16.7% Forecast only 0 0.0% No public exploit 15 83.3%
split by peak 5 / quarter
No exploit published: 17Protected by Waratek: 1 Medium: 18 not blocked: 17blocked by ARMR today: 1 No public exploit: 15Proof of concept only: 3
Q1 211 No exploit published1 Medium1 not blocked1 No public exploit1 Q2 210 Q3 210 Q4 210 Q1 221 No exploit published1 Medium1 not blocked1 No public exploit1 Q2 220 Q3 225 Protected by Waratek1 No exploit published4 Medium5 blocked by ARMR today1 not blocked4 Proof of concept only1 No public exploit4 Q4 223 No exploit published3 Medium3 not blocked3 No public exploit3 Q1 230 Q2 231 No exploit published1 Medium1 not blocked1 Proof of concept only1 Q3 230 Q4 232 No exploit published2 Medium2 not blocked2 Proof of concept only1 No public exploit1 Q1 241 No exploit published1 Medium1 not blocked1 No public exploit1 Q2 241 No exploit published1 Medium1 not blocked1 No public exploit1 Q3 240 Q4 240 Q1 250 Q2 250 Q3 250 Q4 250 Q1 260 Q2 261 No exploit published1 Medium1 not blocked1 No public exploit1 Q3 261 No exploit published1 Medium1 not blocked1 No public exploit1 Q4 261 No exploit published1 Medium1 not blocked1 No public exploit1
Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
18 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2026-116590 Medium 2026-10-26 No exploit published No public exploit snappy-java is a Java port of the snappy, a fast C++ compresser/decompresser developed by Google. Prior to 1.1.10.9, Snappy.arrayCopy(Object src, int offset, int byteLength, Object dest, int destOffset) passes caller-supplied ranges to native memcpy without validating either array, allowing negative or oversized byteLength and offset values to read or write outside array bounds and crash the JVM. SnappyOutputStream.rawWrite and SnappyInputStream.rawRead, including their typed-array write and read methods, pass caller-controlled ranges through this primitive, and typed-array byte-size calculations can overflow int. This issue is fixed in version 1.1.10.9.
CVE-2026-93451 Medium 2026-09-18 No exploit published No public exploit snappy-java through 1.1.10.8 contains a buffer overflow vulnerability in typed Snappy.uncompress*Array methods that allocate output arrays by dividing uncompressed length by element size but pass the undivided length to native code. Attackers controlling compressed input can cause misaligned length values to write past array bounds with attacker-controlled bytes, corrupting heap memory.
CVE-2026-48040 Medium 2026-06-04 No exploit published No public exploit The netty incubator codec.bhttp is a java language binary http parser. The library implements Oblivious HTTP (RFC 9458) using BoringSSL's HPKE C library via JNI. When deriving native memory addresses for cryptographic operations versions prior to 0.0.22.Final provide a fallback path for direct ByteBufs that do not expose their memory address through `hasMemoryAddress()`. This fallback occurs when `sun.misc.Unsafe` is unavailable to Netty — for example, when the JVM is started with `-Dio.netty.noUnsafe=true`, when a SecurityManager restricts Unsafe access, or when running on non-HotSpot JVMs. In these configurations, Netty's default `PooledByteBufAllocator` returns `PooledDirectByteBuf` instances for which `hasMemoryAddress()` returns false. Under the enabling JVM configuration, an unauthenticated network attacker can cause the OHTTP gateway to corrupt memory belonging to other concurrent connections and disclose the contents of adjacent pooled direct buffers by triggering cryptographic operations with crafted OHTTP requests. The corruption occurs regardless of whether the AEAD tag verification succeeds, as BoringSSL zeroizes the output buffer on failure. The information disclosure path provides the attacker with the encryption key needed to extract the leaked data. This violates the confidentiality and integrity of all connections sharing the same Netty buffer arena. Version 0.0.22.Final fixes the issue.
CVE-2024-37280 Medium 2024-06-13 No exploit published No public exploit A flaw was discovered in Elasticsearch, affecting document ingestion when an index template contains a dynamic field mapping of “passthrough” type. Under certain circumstances, ingesting documents in this index would cause a StackOverflow exception to be thrown and ultimately lead to a Denial of Service. Note that passthrough fields is an experimental feature.
CVE-2024-29133 Medium 2024-03-21 No exploit published No public exploit Out-of-bounds Write vulnerability in Apache Commons Configuration.This issue affects Apache Commons Configuration: from 2.0 before 2.10.1. Users are recommended to upgrade to version 2.10.1, which fixes the issue.
CVE-2023-50572 Medium 2023-12-29 No exploit published Proof of concept only An issue in the component GroovyEngine.execute of jline-groovy v3.24.1 allows attackers to cause an OOM (OutofMemory) error.
CVE-2023-51074 Medium 2023-12-27 No exploit published No public exploit json-path v2.8.0 was discovered to contain a stack overflow via the Criteria.parse() method.
CVE-2023-33546 Medium 2023-06-01 No exploit published Proof of concept only Janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when using the expression evaluator.guess parameter name method. If the parser runs on user-supplied input, an attacker could supply content that causes the parser to crash due to a stack overflow. NOTE: this is disputed by multiple parties because Janino is not intended for use with untrusted input.
CVE-2022-41854 Medium 2022-11-11 No exploit published No public exploit Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
CVE-2022-40160 Medium 2022-10-06 No exploit published No public exploit ** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google in breach of the CNA rules. After review by the JXPath maintainers, the original report was found to be invalid.
CVE-2022-40159 Medium 2022-10-06 No exploit published No public exploit ** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google in breach of the CNA rules. After review by the JXPath maintainers, the original report was found to be invalid.
CVE-2022-38752 Medium 2022-09-05 Protected by Waratek Proof of concept only Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow.
CVE-2022-38751 Medium 2022-09-05 No exploit published No public exploit Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
CVE-2022-38750 Medium 2022-09-05 No exploit published No public exploit Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
CVE-2022-38749 Medium 2022-09-05 No exploit published No public exploit Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
CVE-2021-4040 Medium 2022-08-24 No exploit published No public exploit A flaw was found in AMQ Broker. This issue can cause a partial interruption to the availability of AMQ Broker via an Out of memory (OOM) condition. This flaw allows an attacker to partially disrupt availability to the broker through a sustained attack of maliciously crafted messages. The highest threat from this vulnerability is system availability.
CVE-2022-24197 Medium 2022-02-01 No exploit published No public exploit iText v7.1.17 was discovered to contain a stack-based buffer overflow via the component ByteBuffer.append, which allows attackers to cause a Denial of Service (DoS) via a crafted PDF file.
CVE-2021-21043 Medium 2021-02-02 No exploit published No public exploit ACS Commons version 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly. An attacker could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. Exploitation of this issue requires user interaction in order to be successful.