ChromeWeb browser · Google
CVE-2022-1500
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 · uneditedInsufficient data validation in Dev Tools in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to bypass content security policy 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 confidenceThis vulnerability in Google Chrome Dev Tools prior to version 101.0.4951.41 involved insufficient data validation that allowed a remote attacker to bypass Content Security Policy (CSP) protections via a specially crafted HTML page. The flaw resided in the Dev Tools component, which failed to properly validate data before processing, enabling CSP bypass.
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
< 101.0.4951.41CVSS 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 your Chrome versionOpen Chrome, click the three-dot menu in the top right, go to Help > About Google Chrome. The version number is displayed on that page.Affected if The version displayed is earlier than 101.0.4951.41 (for example, 100.x.x.x or any version below 101.0.4951.41)
-
Confirm Dev Tools accessibilityOpen any webpage in Chrome, then press F12 or right-click and select Inspect to open Developer Tools. This confirms the Dev Tools component is available.Affected if Dev Tools opens successfully - the vulnerability resides in this component and it is enabled by default in Chrome.
-
Review recent browser usageCheck if you have recently opened untrusted or externally-sourced HTML pages while Dev Tools was accessible. This is the attack vector described in the CVE.Affected if You have opened untrusted HTML files or visited questionable websites while using an affected Chrome version.
You are affected if your installed Google Chrome version is earlier than 101.0.4951.41 and you use the Dev Tools functionality.
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 · scoped101.0.4951.41
Update Google Chrome to version 101.0.4951.41 or later to patch the insufficient data validation in Dev Tools. Users should also be cautious when opening untrusted HTML pages that could exploit Dev Tools functionality.
Chrome 101.0.4951.41
- Open Google Chrome browser
- Click the menu icon (three dots) in the top-right corner or go to Help > About Google Chrome
- Chrome will automatically check for updates and display the current version
- If an update is available to version 101.0.4951.41 or later, click 'Update Google Chrome'
- Restart the browser to apply the update
- Verify the update by returning to Help > About Google Chrome and confirming the version is 101.0.4951.41 or higher
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
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 locallyCheck whether your project pulls in CVE-2022-1500 — 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-2022-1500 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