ChromeWeb browser · Google
CVE-2024-0812
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 Accessibility in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (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 · moderate confidenceThis vulnerability exists in the Accessibility component of Google Chrome versions prior to 121.0.6167.85. An inappropriate implementation flaw allows a remote attacker to potentially exploit object corruption (likely a use-after-free or similar memory safety issue) by tricking a user into visiting a crafted malicious HTML page.
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
< 121.0.6167.85
FedoraOperating system
= 38= 39CVSS 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 versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The displayed version is lower than 121.0.6167.85 (for example, 121.0.6167.74, 120.x.x.x, etc.)
-
Verify Chrome version on Fedora 38Run command: rpm -qa | grep google-chrome on Fedora 38 systemAffected if The installed package version is lower than 121.0.6167.85-1
-
Verify Chrome version on Fedora 39Run command: rpm -qa | grep google-chrome on Fedora 39 systemAffected if The installed package version is lower than 121.0.6167.85-1
-
Confirm Chrome is the browser in useCheck if Google Chrome is the default browser or commonly used browser on the systemAffected if Chrome is actively used and the version is in the affected range < 121.0.6167.85
You are affected if you are running any version of Google Chrome prior to 121.0.6167.85 on Windows, macOS, Linux, or on Fedora 38/39 systems with vulnerable Chrome packages installed.
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 · scoped121.0.6167.85
Update Google Chrome to version 121.0.6167.85 or later. Users should ensure automatic updates are enabled or manually check for updates via Chrome's Help > About Google Chrome.
Chrome 121.0.6167.85 or later
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is earlier than 121.0.6167.85, click 'Update Google Chrome' to install the latest version
- Restart Chrome after the update completes
- For Fedora systems, run 'sudo dnf update chromium' or 'sudo dnf update' to install the patched Chromium package
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-2024-0812 — 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-0812 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