Skip to content
Fencer Intel
medium 6.5

CVE-2021-37976 kev in the critical feed json

Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive inf…

published 5y ago modified 4mo ago also EUVD-2021-24449

cvss
6.5
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
19.9%
EPSS 19.9% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.

Patch / fix

cisa required action Apply updates per vendor instructions.

  • Google Chrome 94.0.4606.71
  • chromium Debian 14, Debian 13, Debian 12 97.0.4692.71-0.1

debian advisories DEBIAN-CVE-2021-37976

  • chromium-browser Ubuntu 18.04 LTS 94.0.4606.71-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2021-37976

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium openSUSE Tumbleweed 94.0.4606.71-1.1
  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1
  • opera openSUSE Leap 15.4 NonFree 85.0.4341.28-lp154.2.5.1
  • opera openSUSE Leap 15.3 NonFree 80.0.4170.63-lp153.2.27.1
  • opera openSUSE Leap 15.2 NonFree 80.0.4170.63-lp152.2.73.1
  • opera openSUSE Leap 15.3 NonFree, openSUSE Leap 15.2 NonFree 80.0.4170.16-lp153.2.24.1
  • chromium openSUSE Leap 15.2 94.0.4606.81-lp152.2.132.1
  • chromium Package Hub 15 SP3, openSUSE Leap 15.3 94.0.4606.71-bp153.2.31.1

opensuse advisories openSUSE-SU-2024:11555-1openSUSE-SU-2024:12948-1openSUSE-SU-2022:0110-1openSUSE-SU-2021:1434-1openSUSE-SU-2021:1433-1openSUSE-SU-2021:1358-1

  • chromium Arch Linux 94.0.4606.71-1
  • vivaldi Arch Linux 4.2.2406.54-1

arch linux advisories AVG-2433AVG-2435

Is CVE-2021-37976 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-37976 updated cvss 8.8

chromium-browser: Information leak in core

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Found exploited as a 0-day (Project Zero)
  2. 0-day patched (Project Zero)
  3. Published
  4. Added to CISA KEV
  5. CISA patch deadline
  6. CISA SSVC: exploitation active

Known exploited

Added
5y ago
Patch by
2021-11-17 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Google, Chromium
CISA name
Google Chromium Information Disclosure Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Found
2021-09-21
Patched
2021-09-30
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

19.90% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • crbug.com https://crbug.com/1251787 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.