13 results · Feed
-
High 8.8
libwebp: OOB write in BuildHuffmanTable
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)
KEV Sep 13, 2023 -
Medium 5.3CVE-2023-1999 Public exploit
Use after free in libwebp
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 encode…
-
Unscored —
A use of uninitialized value was found in libwebp in versions before 1.0.1 in ReadSymbol().
-
Unscored —
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ShiftBytes().
-
Unscored —
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24().
-
Unscored —
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in PutLE16().
-
Unscored —
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ApplyFilter().
-
Unscored —
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE16().
-
Unscored —
A flaw was found in libwebp in versions before 1.0.1. When reading a file libwebp allocates an excessive amount of memo…
-
Unscored —
A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkAssignData. The …
-
Unscored —
A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkVerifyAndAssign.…
-
Unscored —
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…
-
Unscored —
A flaw was found in libwebp in versions before 1.0.1. A heap-based buffer overflow in function WebPDecodeRGBInto is pos…