Overview 24 matches · 0 in Waratek scope · 0 protected · 1 exploited · 1 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
24matches
0in Waratek scope0.0%
0protected0.0%
1exploited4.2%
1CISA KEV4.2%
1public PoC4.2%
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
0
0.0%
Not applicable
24
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
24
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
4.2%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
23
95.8%
split by
peak 11 / year
20101
Not applicable1
Critical1
not blocked1
No public exploit1
20110
20121
Not applicable1
Medium1
not blocked1
No public exploit1
20130
20140
20150
20160
20171
Not applicable1
Low1
not blocked1
No public exploit1
20183
Not applicable3
Critical1
High1
Medium1
not blocked3
No public exploit3
20192
Not applicable2
High2
not blocked2
No public exploit2
20200
202111
Not applicable11
Critical10
High1
not blocked11
No public exploit11
20220
20233
Not applicable3
High3
not blocked3
Exploited1
No public exploit2
20242
Not applicable2
Medium2
not blocked2
No public exploit2
20102012201420162018202020222024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-5197 | Medium | 2024-06-03 | Not applicable | No public exploit | There exists interger overflows in libvpx in versions prior to 1.14.1. Calling vpx_img_alloc() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned vpx_image_t struct may be invalid. Calling vpx_img_wrap() with a large value of the d_w, d_h, or stride_align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned vpx_image_t struct may be invalid. We recommend upgrading to version 1.14.1 or beyond |
| CVE-2023-6349 | Medium | 2024-05-27 | Not applicable | No public exploit | A heap overflow vulnerability exists in libvpx - Encoding a frame that has larger dimensions than the originally configured size with VP9 may result in a heap overflow in libvpx. We recommend upgrading to version 1.13.1 or above |
| CVE-2023-44488 | High | 2023-09-30 | Not applicable | No public exploit | VP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding. |
| CVE-2023-5217 | High | 2023-09-28 | Not applicable | Exploited | Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) |
| CVE-2023-1999 | High | 2023-06-20 | Not applicable | No public exploit | There exists a use after free/double free in libwebp. An attacker can use the ApplyFiltersAndEncode() function and loop through to free best.bw and assign best = trial pointer. The second loop will then return 0 because of an Out of memory error in VP8 encoder, the pointer is still assigned to trial and the AddressSanitizer will attempt a double free. |
| CVE-2020-36332 | High | 2021-05-21 | Not applicable | No public exploit | A flaw was found in libwebp in versions before 1.0.1. When reading a file libwebp allocates an excessive amount of memory. The highest threat from this vulnerability is to the service availability. |
| CVE-2020-36331 | Critical | 2021-05-21 | Not applicable | No public exploit | A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkAssignData. The highest threat from this vulnerability is to data confidentiality and to the service availability. |
| CVE-2020-36330 | Critical | 2021-05-21 | Not applicable | No public exploit | A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkVerifyAndAssign. The highest threat from this vulnerability is to data confidentiality and to the service availability. |
| CVE-2020-36329 | Critical | 2021-05-21 | Not applicable | No public exploit | A flaw was found in libwebp in versions before 1.0.1. A use-after-free was found due to a thread being killed too early. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. |
| CVE-2020-36328 | Critical | 2021-05-21 | Not applicable | No public exploit | A flaw was found in libwebp in versions before 1.0.1. A heap-based buffer overflow in function WebPDecodeRGBInto is possible due to an invalid check for buffer size. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. |
| CVE-2018-25014 | Critical | 2021-05-21 | Not applicable | No public exploit | A use of uninitialized value was found in libwebp in versions before 1.0.1 in ReadSymbol(). |
| CVE-2018-25013 | Critical | 2021-05-21 | Not applicable | No public exploit | A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ShiftBytes(). |
| CVE-2018-25012 | Critical | 2021-05-21 | Not applicable | No public exploit | A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24(). |
| CVE-2018-25011 | Critical | 2021-05-21 | Not applicable | No public exploit | A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in PutLE16(). |
| CVE-2018-25010 | Critical | 2021-05-21 | Not applicable | No public exploit | A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ApplyFilter(). |
| CVE-2018-25009 | Critical | 2021-05-21 | Not applicable | No public exploit | A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE16(). |
| CVE-2016-9969 | High | 2019-05-23 | Not applicable | No public exploit | In libwebp 0.5.1, there is a double free bug in libwebpmux. |
| CVE-2019-9746 | High | 2019-03-13 | Not applicable | No public exploit | In libwebm before 2019-03-08, a NULL pointer dereference caused by the functions OutputCluster and OutputTracks in webm_info.cc will trigger an abort, which allows a DoS attack, a similar issue to CVE-2018-19212. |
| CVE-2018-19212 | Medium | 2018-11-12 | Not applicable | No public exploit | In libwebm through 2018-10-03, there is an abort caused by libwebm::Webm2Pes::InitWebmParser() that will lead to a DoS attack. |
| CVE-2018-6548 | Critical | 2018-02-02 | Not applicable | No public exploit | A use-after-free issue was discovered in libwebm through 2018-02-02. If a Vp9HeaderParser was initialized once before, its property frame_ would not be changed because of code in vp9parser::Vp9HeaderParser::SetFrame. Its frame_ could be freed while the corresponding pointer would not be updated, leading to a dangling pointer. This is related to the function OutputCluster in webm_info.cc. |
| CVE-2018-6406 | High | 2018-01-30 | Not applicable | No public exploit | The function ParseVP9SuperFrameIndex in common/libwebm_util.cc in libwebm through 2018-01-30 does not validate the child_frame_length data obtained from a .webm file, which allows remote attackers to cause an information leak or a denial of service (heap-based buffer over-read and later out-of-bounds write), or possibly have unspecified other impact. |
| CVE-2016-9085 | Low | 2017-02-03 | Not applicable | No public exploit | Multiple integer overflows in libwebp allows attackers to have unspecified impact via unknown vectors. |
| CVE-2012-0823 | Medium | 2012-02-23 | Not applicable | No public exploit | VP8 Codec SDK (libvpx) before 1.0.0 "Duclair" allows remote attackers to cause a denial of service (application crash) via (1) unspecified "corrupt input" or (2) by "starting decoding from a P-frame," which triggers an out-of-bounds read, related to "the clamping of motion vectors in SPLITMV blocks". |
| CVE-2010-4203 | Critical | 2010-11-06 | Not applicable | No public exploit | WebM libvpx (aka the VP8 Codec SDK) before 0.9.5, as used in Google Chrome before 7.0.517.44, allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via invalid frames. |