dbcve.org
ChromeWeb browser · Google

CVE-2024-0813

HIGH · 8.8 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to 121.0.6167.85 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in Reading Mode in Google Chrome prior to 121.0.6167.85 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via specific UI interaction. (Chromium security severity: Medium)

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 confidence

A use-after-free vulnerability exists in Google Chrome's Reading Mode feature prior to version 121.0.6167.85. Attackers could exploit this by tricking users into installing a malicious extension, then triggering specific UI interactions to corrupt heap memory.

MitigationUpdate Google Chrome to version 121.0.6167.85 or later. Review and restrict extension installation permissions to prevent users from installing untrusted extensions.

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
Affected:< 121.0.6167.85
FedoraOperating system
Affected:= 38= 39

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Google Chrome is installed
    On Windows, check for Chrome in Program Files or via 'chrome --version' in command prompt. On Linux, run 'google-chrome --version' or check package manager. On macOS, check /Applications/Google Chrome.app or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version'
    Affected if Google Chrome is present on the system
  2. Determine installed Chrome version
    Run 'google-chrome --version' on Linux, 'chrome --version' on Windows command prompt, or 'Google Chrome -> Help -> About Google Chrome' in the browser
    Affected if Version is lower than 121.0.6167.85
  3. Check if Reading Mode feature has been used
    In Chrome, look for the reading mode icon in the address bar (appears as a book/document icon) or check browser history/bookmarks for pages opened in reading mode. Alternatively, check for reading mode extensions installed
    Affected if Reading Mode has been invoked or a reading mode extension is active
  4. Verify malicious extension installation possibility
    In Chrome, navigate to chrome://extensions and check for any unknown or untrusted extensions. Review if users have permission to install extensions freely
    Affected if Untrusted or malicious extensions can be installed or are already present
  5. Confirm Fedora version if applicable
    Run 'cat /etc/fedora-release' or 'rpm -q fedora-release' to identify the Fedora version
    Affected if System is Fedora 38 or Fedora 39 and Chrome version is below 121.0.6167.85

User is affected if Google Chrome version is below 121.0.6167.85 AND the Reading Mode feature is accessible or a malicious extension can be installed on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 121.0.6167.85 or later
Fixed in 121.0.6167.85
Interim mitigation

Update Google Chrome to version 121.0.6167.85 or later. Review and restrict extension installation permissions to prevent users from installing untrusted extensions.

Recommended fix High confidence

Chrome 121.0.6167.85 or later (Fedora: google-chrome-stable packages for F38/F39)

  1. Open Google Chrome and navigate to chrome://settings/help
  2. Click 'Check for updates' or wait for Chrome to automatically check
  3. If version 121.0.6167.85 or later is available, click 'Update Google Chrome'
  4. Restart the browser to complete the update
  5. For Fedora systems: run 'sudo dnf update google-chrome-stable' to receive the patched package
Caveat Minimal risk - this is a security patch update within the same major version

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 / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0813 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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