CVE ID | Published | Description | Score | Severity |
---|---|---|---|---|
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) | 8.8 |
High |
||
A use of uninitialized value was found in libwebp in versions before 1.0.1 in ReadSymbol(). | 9.8 |
Critical |
||
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ShiftBytes(). | 9.1 |
Critical |
||
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24(). | 9.1 |
Critical |
||
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in PutLE16(). | 9.8 |
Critical |
||
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ApplyFilter(). | 9.1 |
Critical |
||
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE16(). | 9.1 |
Critical |
||
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. | 7.5 |
High |
||
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. | 9.1 |
Critical |
||
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. | 9.1 |
Critical |
||
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. | 9.8 |
Critical |
||
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. | 9.8 |
Critical |
||
Multiple integer overflows in libwebp allows attackers to have unspecified impact via unknown vectors. | 3.3 |
Low |