CyberSecBulletin
CVE-2021-37976Exploited in the wildNVD status: Analyzed

Google Chromium Information Disclosure

Published Updated By the CyberSecBulletin desk

CVE-2021-37976 is a medium-severity missing authorization vulnerability in Chrome from Google, with a CVSS 3.1 base score of 6.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 94.0.4606.71 as the first without the flaw, so updating Chrome to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on November 3, 2021, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Chrome to 94.0.4606.71 or a later version.
  2. CISA's required action: Apply updates per vendor instructions.
  3. Read the advisory on crbug.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  5. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
GoogleChromebefore 94.0.4606.7194.0.4606.71
Fedora ProjectFedora33; 34; 35Not stated
DebianDebian Linux10.0; 11.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.5MediumNVD
CVSS 3.16.5MediumCISA (ADP)
CVSS 2.04.3MediumNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Missing Authorization vulnerabilities (CWE-862)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: partial).
  5. Record last changed materially (score, affected products, status or references).

References

Advisories

Third-party and government advisories

Other vulnerabilities in Chrome

All Chrome vulnerabilities

Recent Missing Authorization vulnerabilities

Spotted an error? Tell us.