Chromium vulnerabilities
We track 4 vulnerabilities in Chromium products across 3 products. 4 are rated high or critical, and none are known to be exploited. The most recent was published on June 3, 2024.
Latest Chromium vulnerabilities
- 9.1 Critical severity
libvpx: Integer Overflow or Wraparound
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 returne
- 7.5 High severity
libvpx: Out-of-bounds Write
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
- 7.5 High severity
libwebp: Double Free
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
- 8.8 High severity
Chrome: Use After Free
Use after free in ANGLE in Google Chrome prior to 111.0.5563.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)