ChromeWeb browser · Google
CVE-2022-3449
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 · uneditedUse after free in Safe Browsing in Google Chrome prior to 106.0.5249.119 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension. (Chromium security severity: High)
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 · high confidenceA use-after-free vulnerability exists in Chrome's Safe Browsing feature prior to version 106.0.5249.119. The flaw is triggered when a user installs a malicious Chrome extension, which can then exploit heap corruption through the Safe Browsing component.
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
< 106.0.5249.119CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 use 'Chrome --version' from command line to view the installed versionAffected if The installed version is earlier than 106.0.5249.119
-
Verify Safe Browsing statusNavigate to chrome://settings/security and locate the Safe Browsing setting, or check the policy 'SafeBrowsingEnabled' in chrome://policyAffected if Safe Browsing is enabled (the vulnerability exists within this component)
-
Review extension installation policyCheck Chrome policy settings for 'ExtensionInstallSources' or 'ExtensionInstallForcelist' in chrome://policy, or review group policies configured in the operating systemAffected if Users are permitted to install extensions from sources other than trusted enterprise-managed stores
The environment is affected if Chrome version is below 106.0.5249.119 AND Safe Browsing is enabled AND users can install extensions, allowing a malicious extension to trigger the use-after-free in Safe Browsing.
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 · scoped106.0.5249.119
Update Google Chrome to version 106.0.5249.119 or later. Additionally, review and restrict Chrome extension installation policies to prevent users from installing untrusted extensions.
Chrome 106.0.5249.119 or later stable release
- Open Google Chrome browser
- Click on the three-dot menu icon in the top-right corner
- Select 'Settings' from the dropdown menu
- In the left sidebar, click 'About Chrome'
- Chrome will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- Wait for the download to complete
- Click 'Relaunch' to restart Chrome and apply the update
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-3449 — 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-3449 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