CVE-2024-7964 json
Use after free in Passwords in Google Chrome on Android prior to 128.0.6613.84 allowed a remote attacker to potentially exploit heap corrup…
published 2024-08-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-48797
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
Use 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)
Patch / fix
- Google Chrome 128.0.6613.84
- chromium Debian 12 128.0.6613.84-1~deb12u1
- chromium Debian 14, Debian 13 128.0.6613.84-1
debian advisories DEBIAN-CVE-2024-7964
- chromium Package Hub 15 SP6, Package Hub 15 SP5, openSUSE Leap 15.6 +1 more 128.0.6613.84-bp156.2.17.1
- chromium openSUSE Tumbleweed 128.0.6613.84-1.1
opensuse advisories openSUSE-SU-2024:0258-1openSUSE-SU-2024:0258-2openSUSE-SU-2024:14285-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
chromereleases.googleblog.com
/2024/08/stable-channel-update-for-desktop_21.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/358296941
permissions-required
Sources
- CVE List CVE-2024-7964
- NVD CVE-2024-7964
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.