dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 6 Jun 2024.
ChromeWeb browser · Google

CVE-2024-4761

HIGH · 8.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 124.0.6367.207 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
Out of bounds write in V8 in Google Chrome prior to 124.0.6367.207 allowed a remote attacker to perform an out of bounds memory write 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

Out-of-bounds write vulnerability in the V8 JavaScript engine in Google Chrome versions prior to 124.0.6367.207. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, allowing memory corruption that could potentially lead to arbitrary code execution.

MitigationUpdate Google Chrome to version 124.0.6367.207 or later. Organizations managing Chrome deployments should push the update through their patch management systems.

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

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 Google Chrome version on Windows/Mac/Linux
    Navigate to chrome://version in the Chrome address bar or run 'google-chrome --version' from command line
    Affected if Installed version is earlier than 124.0.6367.207 (e.g., 124.0.6367.198 or lower)
  2. Check Chromium version on Linux systems
    Run 'chromium --version' or 'chromium-browser --version' from command line
    Affected if Installed version is earlier than 124.0.6367.207
  3. Verify V8 JavaScript engine is in use
    Open any webpage in Chrome, press F12 to open DevTools, then go to the Console tab and type 'console.log(V8_VERSION)' or 'console.log(process.versions.v8)' if Node.js context is available
    Affected if V8 is present (this is the default and cannot be disabled in Chrome, so the check confirms the vulnerable component is active)
  4. Check Fedora system package version
    Run 'dnf list installed | grep -i chromium' or 'rpm -qa | grep -i chromium' on Fedora systems
    Affected if Installed chromium or google-chrome package version is earlier than 124.0.6367.207

You are affected if Chrome/Chromium version is lower than 124.0.6367.207 and you use the V8 JavaScript engine (default in Chrome), which allows crafted HTML pages to trigger the out-of-bounds write.

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 124.0.6367.207 or later
Fixed in 124.0.6367.207
Interim mitigation

Update Google Chrome to version 124.0.6367.207 or later. Organizations managing Chrome deployments should push the update through their patch management systems.

Recommended fix High confidence

Chrome 124.0.6367.207 (or later)

  1. Upgrade Google Chrome to version 124.0.6367.207 or later by navigating to Chrome menu > Help > About Google Chrome and allowing it to check for updates, or download the latest version from the official Google Chrome website.
  2. For Fedora systems, ensure your system packages are updated: run 'sudo dnf update' or 'sudo dnf upgrade' to apply the latest security patches for the chromium package.
  3. Verify the Chrome version by navigating to chrome://settings/help after upgrading to confirm version 124.0.6367.207 or later is installed.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get it fixed fast

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-4761 — 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-4761 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