Heap corruption via DOMStorage double free
Published Sep 29, 2022 · Updated May 20, 2025
Double free in DOMStorage in Google Chrome before 73.0.3683.75 allows remote attackers to corrupt heap memory via crafted HTML. A race in DOMStorage causes the same allocation to be freed twice while processing page-controlled storage operations. A user must render attacker-controlled HTML; successful exploitation corrupts browser memory, while public records do not establish a browser-sandbox escape.
Summary
What happened
Double free in DOMStorage in Google Chrome before 73.0.3683.75 allows remote attackers to corrupt heap memory via crafted HTML. A race in DOMStorage causes the same allocation to be freed twice while processing page-controlled storage operations. A user must render attacker-controlled HTML; successful exploitation corrupts browser memory, while public records do not establish a browser-sandbox escape.
The record
- CVE
- CVE-2019-5797
- Published
- Sep 29, 2022
- Updated
- May 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-415, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2022CVE publishedPublication date reported by the CVE source.
- May 20, 2025Record 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 <73.0.3683.75
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.
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