Heap corruption via Web Payments use-after-free
Published Feb 22, 2023 · Updated Feb 13, 2025
Use after free in Google Chrome's Web Payments API on Android before 110.0.5481.177 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the Web Payments API as the locus but has not disclosed which object's lifetime is mismanaged or where freed memory is reused. Exploitation requires an already compromised renderer process, and the published evidence does not establish escape from the renderer sandbox.
Summary
What happened
Use after free in Google Chrome's Web Payments API on Android before 110.0.5481.177 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the Web Payments API as the locus but has not disclosed which object's lifetime is mismanaged or where freed memory is reused. Exploitation requires an already compromised renderer process, and the published evidence does not establish escape from the renderer sandbox.
The record
- CVE
- CVE-2023-0927
- Published
- Feb 22, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=0 <110.0.5481.177
- Affected versionversion=110.0.5481.177 <110.0.5481.177
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