dbcve.org
ChromeWeb browser · Google

CVE-2024-3834

HIGH · 8.8 CVSS v3.1 Published 2024-04-17
Fix available
A fix is available. Upgrade to 124.0.6367.60 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 Downloads in Google Chrome prior to 124.0.6367.60 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

Use-after-free vulnerability in the Downloads component of Google Chrome prior to version 124.0.6367.60 allows a remote attacker to potentially exploit heap corruption via a crafted HTML page, possibly leading to code execution.

MitigationUpdate Google Chrome to version 124.0.6367.60 or later. This is a client-side browser vulnerability requiring browser updates rather than server-side remediation.

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.60

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. Verify Google Chrome is installed
    Check for Chrome installation by looking for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\ or %LOCALAPPDATA%\Google\Chrome\Application\) or by running 'chrome --version' from command line
    Affected if Google Chrome browser is present on the system
  2. Determine installed Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'chrome --version' from command line, or right-click chrome.exe and select Properties > Details to view File Version
    Affected if Unable to determine the installed version number
  3. Compare version against affected range
    Parse the version number found in the previous step. The affected range is any version less than 124.0.6367.60 (e.g., 124.0.6367.59, 123.x.x.x, 122.x.x.x, etc.)
    Affected if Installed version is less than 124.0.6367.60 (for example, 123.0.6367.78 or any earlier version)
  4. Confirm Downloads component is in use
    The Downloads component in Chrome handles downloaded files and is a core browser feature enabled by default. Verify it is accessible by visiting chrome://downloads or attempting to download a file
    Affected if Downloads component is accessible (this is the default state for Chrome installations)

User is affected if Google Chrome is installed with any version lower than 124.0.6367.60 and the Downloads component is in use (the default state for Chrome browsers).

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.60 or later
Fixed in 124.0.6367.60
Interim mitigation

Update Google Chrome to version 124.0.6367.60 or later. This is a client-side browser vulnerability requiring browser updates rather than server-side remediation.

Recommended fix High confidence

Chrome 124.0.6367.60 or later

  1. Open Google Chrome browser
  2. Navigate to Settings by clicking the three-dot menu in the top-right corner
  3. Scroll down and click 'About Chrome' in the left sidebar
  4. Chrome will automatically check for updates; if version 124.0.6367.60 or later is available, click 'Update Google Chrome'
  5. Restart the browser to apply the update
  6. Verify the version by returning to 'About Chrome' and confirming the version number is 124.0.6367.60 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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