Process-memory disclosure via crash-reporting stack overflow
Published Mar 7, 2023 · Updated Oct 15, 2024
Stack buffer overflow in Google Chrome before 111.0.5563.64 on Windows allows remote attackers to read process memory via crafted HTML. Google identifies Crash reporting as the locus but has not published the affected function or the operation that overruns the stack buffer. Exploitation requires a previously compromised renderer process and is limited to potentially sensitive process-memory disclosure, with no integrity or availability impact reported.
Summary
What happened
Stack buffer overflow in Google Chrome before 111.0.5563.64 on Windows allows remote attackers to read process memory via crafted HTML. Google identifies Crash reporting as the locus but has not published the affected function or the operation that overruns the stack buffer. Exploitation requires a previously compromised renderer process and is limited to potentially sensitive process-memory disclosure, with no integrity or availability impact reported.
The record
- CVE
- CVE-2023-1217
- Published
- Mar 7, 2023
- Updated
- Oct 15, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 7, 2023CVE publishedPublication date reported by the CVE source.
- Oct 15, 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=111.0.5563.64 <111.0.5563.64
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.
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