ChromeWeb browser · Google
CVE-2022-0795
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 · uneditedType confusion in Blink Layout in Google Chrome prior to 99.0.4844.51 allowed a remote attacker to potentially exploit heap corruption 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 · high confidenceType confusion vulnerability in Blink Layout (Chrome's rendering engine) prior to version 99.0.4844.51 allows a remote attacker to execute arbitrary code via a crafted HTML page. The vulnerability can lead to heap corruption, enabling potential code execution or denial of service.
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
< 99.0.4844.51CVSS 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 Google Chrome versionNavigate to chrome://settings/help in the Chrome browser, or use 'About Google Chrome' from the Chrome menu. The version number is displayed on the page that opens.Affected if The displayed version is less than 99.0.4844.51 (for example, 99.0.4844.0, 98.0.4750.0, etc.)
-
Check Chrome version via command line (Windows)Open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v VersionAffected if The returned version value is less than 99.0.4844.51
-
Check Chrome version via command line (macOS)Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The returned version is less than 99.0.4844.51
-
Check Chrome version via command line (Linux)Open Terminal and run: google-chrome --version or chromium --version depending on installationAffected if The returned version is less than 99.0.4844.51
A user is affected if their installed Google Chrome version is any version prior to 99.0.4844.51, as the vulnerability exists in all earlier versions and can be triggered simply by visiting a crafted webpage.
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 · scoped99.0.4844.51
Update Google Chrome to version 99.0.4844.51 or later. Organizations should deploy browser updates through their patch management systems and enforce automatic updates where possible.
99.0.4844.51 or later
- Open Chrome and navigate to Help > About Google Chrome to check current version
- If version is below 99.0.4844.51, click 'Update Google Chrome' or download the latest version from chrome.com
- Restart Chrome after the update completes
- Verify the version now shows 99.0.4844.51 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0795 — 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-0795 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