Cross-origin data disclosure via insufficient CORS enforcement
Published Jan 10, 2023 · Updated Mar 20, 2025
Insufficient CORS policy enforcement in Google Chrome before 109.0.5414.74 allows remote attackers to read cross-origin data via crafted HTML. The public record does not identify the affected CORS code path or explain which policy check fails before cross-origin response data is exposed. Exploitation requires a user to open attacker-controlled HTML, and the documented consequence is limited to unintended cross-origin data disclosure.
Summary
What happened
Insufficient CORS policy enforcement in Google Chrome before 109.0.5414.74 allows remote attackers to read cross-origin data via crafted HTML. The public record does not identify the affected CORS code path or explain which policy check fails before cross-origin response data is exposed. Exploitation requires a user to open attacker-controlled HTML, and the documented consequence is limited to unintended cross-origin data disclosure.
The record
- CVE
- CVE-2023-0141
- Published
- Jan 10, 2023
- Updated
- Mar 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-693, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- Mar 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 <109.0.5414.74
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