LiveActive security incident?Get immediate response
CVE Record

CVE-2021-30571: Insufficient policy enforcement in DevTools in Google Chrome prior to 92.0.4515.107 allowed an attacker who...

Insufficient policy enforcement in DevTools in Google Chrome prior to 92.0.4515.107 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted HTML page.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Chrome before 92.0.4515.107 had a DevTools policy enforcement flaw. If a user installed a malicious extension, an attacker could use a crafted HTML page to potentially escape Chrome’s sandbox. The bundle does not show active exploitation.

Executive priority

Treat as a routine but meaningful browser hardening item. The impact could be serious, but available evidence shows user and extension prerequisites and no KEV-listed exploitation in the provided sources.

Technical view

CVE-2021-30571 is an insufficient policy enforcement issue in Chrome DevTools. The CVE description ties exploitation to a malicious extension plus crafted HTML, with possible sandbox escape. Affected scope is Google Chrome before 92.0.4515.107; Fedora advisories also reference Chromium package updates.

Likely exposure

Exposure is most relevant where Chrome or Chromium stayed below 92.0.4515.107 and users could install untrusted extensions. Managed extension controls reduce practical reach, but vulnerable browser versions remain the key validation target.

Exploitation context

The provided bundle marks KEV as false and does not cite public active exploitation. The described attack requires user-assisted installation of a malicious extension before a crafted HTML page could trigger the sandbox escape path.

Researcher notes

Public detail is limited in the supplied bundle, and the Chromium bug link may not expose full technical context. Focus validation on vulnerable version presence, extension trust controls, and package advisory coverage rather than assuming standalone remote exploitation.

Mitigation direction

  • Update Google Chrome to 92.0.4515.107 or later.
  • Apply relevant Fedora Chromium package updates where Fedora Chromium is deployed.
  • Review enterprise controls for untrusted Chrome extension installation.
  • Check current vendor guidance for any platform-specific remediation details.

Validation and detection

  • Inventory Chrome and Chromium versions across managed endpoints.
  • Confirm no deployed browser remains below 92.0.4515.107.
  • Review extension inventories for untrusted or unauthorized extensions.
  • Verify Linux package update status against the referenced Fedora advisories.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-30571 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChromeunspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.