Overview 8 matches · 0 in Waratek scope · 0 protected · 2 exploited · 2 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
8matches
0in Waratek scope0.0%
0protected0.0%
2exploited25.0%
2CISA KEV25.0%
2public PoC25.0%
1EPSS ≥ 0.512.5%
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
1
12.5%
Not applicable
7
87.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
8
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
25.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
6
75.0%
split by
peak 3 / quarter
Q1 181
Not applicable1
High1
not blocked1
No public exploit1
Q2 180
Q3 180
Q4 180
Q1 191
Not applicable1
High1
not blocked1
No public exploit1
Q2 191
Not applicable1
High1
not blocked1
No public exploit1
Q3 190
Q4 190
Q1 200
Q2 200
Q3 200
Q4 200
Q1 210
Q2 211
Not applicable1
High1
not blocked1
No public exploit1
Q3 210
Q4 210
Q1 220
Q2 220
Q3 220
Q4 220
Q1 230
Q2 231
Not applicable1
High1
not blocked1
No public exploit1
Q3 233
Outside Waratek scope1
Not applicable2
High3
not blocked3
Exploited2
No public exploit1
Q1 18Q3 18Q1 19Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-4863 | High | 2023-09-12 | Outside Waratek scope | Exploited | Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical) |
| 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-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-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. |