ChromeWeb browser · Google
CVE-2022-1868
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 Extensions API in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions 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 confidenceGoogle Chrome's Extensions API had an inappropriate implementation that allowed a malicious extension, once installed, to bypass navigation restrictions when a user visited a crafted HTML page. This represents a security boundary bypass within the browser's extension system.
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
< 102.0.5005.61CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Locate Google Chrome installationCheck for Chrome executable - on Windows look in C:\Program Files\Google\Chrome\Application\, on macOS check /Applications/Google Chrome.app, on Linux check /usr/bin/ or /opt/google/chrome/Affected if Google Chrome browser is installed on the system
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or click Help > About Google Chrome from the menu, or run 'google-chrome --version' from command lineAffected if The version displayed is below 102.0.5005.61 (e.g., 101.x.x.x or earlier versions)
-
Compare version against affected rangeParse the full version number shown (format: major.minor.build.patch). Any version starting with 101 or lower, or any version that cannot be determined to be 102.0.5005.61 or later, should be considered potentially affectedAffected if The installed version number is less than 102.0.5005.61
The environment is affected if Google Chrome is installed and the running version is earlier than 102.0.5005.61
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 · scoped102.0.5005.61
Update Google Chrome to version 102.0.5005.61 or later to receive the patch for this vulnerability. Organizations should ensure browser update mechanisms are active and consider reviewing installed extensions for legitimacy.
Chrome 102.0.5005.61 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for and download the latest update
- Restart Chrome if an update was downloaded
- Verify the version by returning to About Google Chrome - it should show version 102.0.5005.61 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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-1868 — 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-1868 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