ASLR bypass via crafted XML content
Published Jul 28, 2023 · Updated Feb 13, 2025
Inappropriate XML implementation in Google Chrome before 107.0.5304.62 allows remote attackers to bypass ASLR via a crafted HTML page. Google identifies the affected locus only as XML and has not published which parser operation mishandles the crafted content. Exploitation requires a user to load attacker-controlled HTML; the documented consequence is an ASLR bypass rather than direct code execution or data access.
Summary
What happened
Inappropriate XML implementation in Google Chrome before 107.0.5304.62 allows remote attackers to bypass ASLR via a crafted HTML page. Google identifies the affected locus only as XML and has not published which parser operation mishandles the crafted content. Exploitation requires a user to load attacker-controlled HTML; the documented consequence is an ASLR bypass rather than direct code execution or data access.
The record
- CVE
- CVE-2022-4909
- Published
- Jul 28, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 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=107.0.5304.62 <107.0.5304.62
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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