Heap corruption via payments use-after-free
Published May 21, 2020 · Updated Aug 4, 2024
Use-after-free in Google Chrome payments before 81.0.4044.122 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the payments component and stale-object access, but the restricted issue does not publicly identify the object or lifetime error. A victim must load attacker-controlled HTML; the documented consequence is heap corruption, while the public record does not specify exploit behavior beyond it.
Summary
What happened
Use-after-free in Google Chrome payments before 81.0.4044.122 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the payments component and stale-object access, but the restricted issue does not publicly identify the object or lifetime error. A victim must load attacker-controlled HTML; the documented consequence is heap corruption, while the public record does not specify exploit behavior beyond it.
The record
- CVE
- CVE-2020-6459
- Published
- May 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <81.0.4044.122
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo