dbcve.org
ChromeWeb browser · Google

CVE-2022-0461

MEDIUM · 6.5 CVSS v3.1 Published 2022-04-05
Fix available
A fix is available. Upgrade to 98.0.4758.80 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Policy bypass in COOP in Google Chrome prior to 98.0.4758.80 allowed a remote attacker to bypass iframe sandbox via a crafted HTML page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Cross-Origin-Opener-Policy (COOP) bypass vulnerability in Google Chrome. COOP is a security header that controls how documents can open windows to other origins. The vulnerability allowed a remote attacker to bypass iframe sandbox restrictions using a crafted HTML page, potentially enabling cross-origin attacks.

MitigationUpdate Google Chrome to version 98.0.4758.80 or later to remediate this vulnerability. Organizations should ensure browser update policies are in place and functioning.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 98.0.4758.80

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Open Chrome version page
    Navigate to chrome://version in the Chrome address bar and note the version number displayed (the first line shows the full version)
    Affected if The displayed version number is less than 98.0.4758.80 (for example, 97.x.x.x)
  2. Alternative: Check via settings
    Click the three-dot menu, go to Help > About Google Chrome; the version will be shown on that page
    Affected if The shown version is lower than 98.0.4758.80

You are affected if the installed Google Chrome version is less than 98.0.4758.80, as the COOP bypass vulnerability exists in those earlier versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 98.0.4758.80 or later
Fixed in 98.0.4758.80
Interim mitigation

Update Google Chrome to version 98.0.4758.80 or later to remediate this vulnerability. Organizations should ensure browser update policies are in place and functioning.

Recommended fix High confidence

Chrome 98.0.4758.80 (or latest stable release)

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Verify the current version and allow Chrome to check for updates
  3. If version is below 98.0.4758.80, click 'Update Google Chrome' and restart the browser
  4. Alternatively, download Chrome 98.0.4758.80 or later from the official Chrome download page

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0461 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data