dbcve.org
ChromeWeb browser · Google

CVE-2024-1284

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 121.0.6167.160 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Mojo in Google Chrome prior to 121.0.6167.160 allowed a remote attacker to potentially exploit heap 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 · high confidence

A use-after-free vulnerability exists in the Mojo component of Google Chrome versions prior to 121.0.6167.160. This memory safety flaw allows a remote attacker to access freed heap memory via a specially crafted HTML page, potentially leading to heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 121.0.6167.160 or later. Organizations should ensure endpoints are running current browser versions through patch management or enterprise update mechanisms.

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.160
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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or on Linux run 'google-chrome --version' or 'chromium --version' in terminal. On Windows, right-click Chrome shortcut and select Help > About Google Chrome.
    Affected if Version is lower than 121.0.6167.160 (e.g., 121.0.6167.85, 120.x.x.x, etc.)
  2. Verify Chrome release channel
    On chrome://settings/help page, note whether the version says 'Stable', 'Beta', 'Dev', or 'Canary'. Each channel has its own version numbering.
    Affected if Channel is Beta, Dev, or Canary with version numbers that map to pre-121.0.6167.160 releases (check corresponding branch dates)
  3. Confirm Mojo component presence
    Mojo is an internal Chromium component for inter-process communication and is enabled by default in all standard Chrome builds. No user-facing config to disable it exists. Visit chrome://components to see if Mojo is listed.
    Affected if Running any standard Chrome build (not Chromium-only builds without Mojo) - this is almost always true for regular Chrome installations
  4. Check Fedora OS version if applicable
    Run 'cat /etc/fedora-release' or 'fedora-release -v' in terminal to determine the Fedora version.
    Affected if System runs Fedora 38 or Fedora 39 AND has Chrome installed from any repository
  5. Identify browser usage context
    Assess whether Chrome is used to render untrusted HTML content from external sources, as the attack requires a specially crafted HTML page.
    Affected if Users browse untrusted websites or open HTML attachments from unknown sources in affected Chrome versions

User is affected if running Google Chrome versions prior to 121.0.6167.160 on any OS, or if Chrome is installed on Fedora 38/39 systems, and the browser processes untrusted HTML content.

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.160 or later
Fixed in 121.0.6167.160
Interim mitigation

Update Google Chrome to version 121.0.6167.160 or later. Organizations should ensure endpoints are running current browser versions through patch management or enterprise update mechanisms.

Recommended fix High confidence

Chrome 121.0.6167.160 or later

  1. Update Google Chrome to version 121.0.6167.160 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome', or download the latest version from google.com/chrome
  2. For Fedora systems, run 'sudo dnf update google-chrome-stable' to install the patched version

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
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1284 — 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-1284 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