ChromeWeb browser · Google
CVE-2024-7964
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 · uneditedUse after free in Passwords in Google Chrome on Android prior to 128.0.6613.84 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 confidenceA use-after-free vulnerability exists in the Passwords component of Google Chrome on Android before version 128.0.6613.84. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, causing the browser to access freed memory and potentially achieve heap corruption and code execution.
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
< 128.0.6613.84CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Google Chrome is installed on the Android deviceNavigate to Settings > Apps > Chrome, or use ADB command: adb shell pm list packages | grep chromeAffected if The package com.android.chrome is present on the device
-
Determine the installed Chrome version on AndroidOpen Chrome > tap three dots > Help & Feedback > Version, OR use ADB: adb shell dumpsys package com.android.chrome | grep versionNameAffected if A version number is returned from either method
-
Compare your installed version against the affected rangeCheck if the version string is less than 128.0.6613.84 (for example, 128.0.6613.83 or earlier)Affected if The installed version is lower than 128.0.6613.84 (for example, 127.0.6613.137, 128.0.6613.83, or any earlier version)
-
Confirm this is Chrome on Android specificallyVerify the affected package is com.android.chrome; other Chromium-based browsers on Android have different package names and may not share the same version numberingAffected if The package name is com.android.chrome and the version falls below 128.0.6613.84
You are affected if Google Chrome for Android (package com.android.chrome) is installed at a version lower than 128.0.6613.84, as the use-after-free in the Passwords component only impacts those versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped128.0.6613.84
Update Google Chrome for Android to version 128.0.6613.84 or later. Organizations should deploy the update through their mobile device management (MDM) infrastructure and verify compliance.
Chrome 128.0.6613.84 or later for Android
- Open Google Play Store on the Android device
- Search for 'Google Chrome' in the app store
- Tap 'Update' to install version 128.0.6613.84 or later
- Alternatively, ensure Google Play Services is functioning properly to allow Chrome's automatic background updates 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
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7964 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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