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 7 Feb 2024.
ChromeWeb browser · Google

CVE-2024-0519

HIGH · 8.8 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 7.2.5 / 120.0.6099.224 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 memory access in V8 in Google Chrome prior to 120.0.6099.224 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

Out-of-bounds memory access vulnerability in Google Chrome's V8 JavaScript engine (versions prior to 120.0.6099.224). A remote attacker can exploit this via a crafted HTML page to potentially corrupt heap memory, leading to possible arbitrary code execution.

MitigationUpdate Google Chrome to version 120.0.6099.224 or later to patch the V8 vulnerability. Organizations should deploy browser updates through their patch management infrastructure.

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:< 120.0.6099.224
FedoraOperating system
Affected:= 38= 39
Couchbase ServerApplication
Affected:< 7.2.5

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, macOS, or Linux
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal to view the installed Chrome version
    Affected if Installed version is lower than 120.0.6099.224
  2. Check Google Chrome package version on Fedora
    Run 'dnf list installed google-chrome' or 'rpm -q google-chrome' to see the installed package version
    Affected if Chrome package is installed on Fedora 38 or 39 with version below 120.0.6099.224
  3. Check Couchbase Server version
    Run 'couchbase-server -version' or check the Couchbase Server admin console under Settings > About for the installed version number
    Affected if Couchbase Server version is lower than 7.2.5
  4. Verify V8 JavaScript engine is in use
    This vulnerability affects the V8 engine which is embedded in Chrome and Couchbase Server; no separate check needed - presence of affected Chrome or Couchbase versions confirms V8 is present
    Affected if Any Chrome version below 120.0.6099.224 or Couchbase version below 7.2.5 is running

Your environment is affected if Google Chrome below version 120.0.6099.224, or Couchbase Server below version 7.2.5, is installed and the V8 JavaScript engine is in use.

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 7.2.5 / 120.0.6099.224 or later
Fixed in 7.2.5120.0.6099.224
Interim mitigation

Update Google Chrome to version 120.0.6099.224 or later to patch the V8 vulnerability. Organizations should deploy browser updates through their patch management infrastructure.

Recommended fix High confidence

Chrome/Chromium: 120.0.6099.224 or later | Couchbase Server: 7.2.5 or later

  1. For Chrome/Chromium-based browsers: Navigate to Chrome menu > Help > About Google Chrome and verify version is 120.0.6099.224 or later. If lower, click 'Update Google Chrome' and restart the browser.
  2. For Couchbase Server: Upgrade to version 7.2.5 or later by following the standard upgrade procedure at docs.couchbase.com (backup data, stop server, install new version, restart).
  3. For Fedora systems: Run 'sudo dnf update' to apply security patches for the V8 engine, then reboot if kernel updates were applied.
Caveat Chrome: None significant for end users. | Couchbase: Review upgrade notes for potential migration steps between major versions.

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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