ChromeWeb browser · Google
CVE-2024-1671
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 · uneditedInappropriate implementation in Site Isolation in Google Chrome prior to 122.0.6261.57 allowed a remote attacker to bypass content security policy via a crafted HTML page. (Chromium security severity: Medium)
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 confidenceA vulnerability in Chrome's Site Isolation feature allowed remote attackers to bypass Content Security Policy (CSP) protections via a specially crafted HTML page. Site Isolation is designed to separate websites into separate processes to prevent cross-site attacks; this flaw enabled malicious pages to circumvent CSP restrictions that normally prevent unauthorized script execution or data access.
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
< 122.0.6261.57CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://settings/help or click Help > About Google Chrome to view the current version numberAffected if The installed version is older than 122.0.6261.57 (e.g., 121.x.x.x or earlier)
-
Verify Site Isolation is enabledNavigate to chrome://flags/#enable-site-per-process and check the Site Isolation flag status; or go to chrome://settings/privacy and verify 'Enhanced protection' is enabled which enforces site isolationAffected if Site Isolation is enabled and the browser version is vulnerable (< 122.0.6261.57)
-
Confirm CSP bypass impactThe vulnerability allows crafted HTML pages to bypass CSP restrictions. Check for any unexpected script executions or data access that would normally be blocked by your configured CSP headersAffected if Content Security Policy headers are defined but scripts execute from untrusted sources, indicating the bypass was successful
You are affected if your Chrome version is below 122.0.6261.57 and Site Isolation is enabled, as the vulnerability specifically exploits the Site Isolation mechanism to bypass CSP protections.
Generated from the published advisory. Verify against your own configuration.
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 · scoped122.0.6261.57
Update Google Chrome to version 122.0.6261.57 or later to obtain the fix for this Site Isolation bypass vulnerability.
Chrome version 122.0.6261.57 (or later stable release)
- Open Google Chrome on your computer
- Click the three-dot menu icon in the top-right corner
- Select 'Help' and then 'About Google Chrome'
- Chrome will check for updates and automatically download the latest version
- Restart Chrome after the update completes
- Verify the version by returning to 'About Google Chrome' - it should show version 122.0.6261.57 or later
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1671 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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