dbcve.org
ChromeWeb browser · Google

CVE-2024-7977

HIGH · 7.8 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to 128.0.6613.84 or later.
See remediation →
81/100
Remediation priority · High
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
Insufficient data validation in Installer in Google Chrome on Windows prior to 128.0.6613.84 allowed a local attacker to perform privilege escalation via a malicious file. (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 · moderate confidence

Insufficient data validation in the Google Chrome installer for Windows allows a local attacker to perform privilege escalation by tricking a user into installing a malicious file. The vulnerability exists in versions prior to 128.0.6613.84 and enables a local attacker to gain elevated privileges on the system.

MitigationUpdate Google Chrome for Windows to version 128.0.6613.84 or later. Organizations should verify current installations and push the update via standard patch management processes.

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:< 128.0.6613.84

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 Chrome is installed on Windows
    Check the Windows Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome or look for chrome.exe in Program Files or Program Files (x86)
    Affected if The registry key or chrome.exe file exists, indicating Chrome is installed on the Windows system
  2. Retrieve installed Chrome version
    Open Chrome and navigate to chrome://help, or right-click chrome.exe and select Properties > Details, or query the Version value from the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if A version number is returned from any of these methods
  3. Compare version against affected range
    Compare the installed version number to 128.0.6613.84 using standard version comparison (major.minor.build.patch)
    Affected if The installed version is less than 128.0.6613.84 (for example, 128.0.6613.83, 127.0.x.x, or earlier)
  4. Check for recent Chrome updates
    In Chrome, go to chrome://settings/help and note the last update date, or check the 'InstallDate' value in the registry under HKLM\SOFTWARE\Google\Update\Clients\{...Google Chrome...}
    Affected if The last update occurred before August 2024 when version 128.0.6613.84 was released

A Windows system with Google Chrome installed is affected if the installed Chrome version is lower than 128.0.6613.84, indicating the vulnerable installer was or is present.

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

Update Google Chrome for Windows to version 128.0.6613.84 or later. Organizations should verify current installations and push the update via standard patch management processes.

Recommended fix High confidence

128.0.6613.84 or later

  1. 1. Open Google Chrome on Windows
  2. 2. Click the three-dot menu icon in the top-right corner
  3. 3. Select 'Help' from the dropdown menu
  4. 4. Click 'About Google Chrome'
  5. 5. Chrome will automatically check for updates and display the current version
  6. 6. If version is below 128.0.6613.84, click 'Update Google Chrome' to download and install the fix
  7. 7. Restart the browser to complete the update

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