Cross-origin data disclosure via CORS policy failure
Published Dec 23, 2021 · Updated Aug 4, 2024
Insufficient CORS policy enforcement in Google Chrome before 96.0.4664.45 allows remote attackers to leak cross-origin data via crafted HTML. The public Chrome advisory identifies the CORS subsystem but does not disclose the faulty policy decision or code path, and the linked Chromium issue requires permission. Exploitation requires a user to load attacker-controlled HTML; the reported consequence is cross-origin data disclosure without integrity or availability impact.
Summary
What happened
Insufficient CORS policy enforcement in Google Chrome before 96.0.4664.45 allows remote attackers to leak cross-origin data via crafted HTML. The public Chrome advisory identifies the CORS subsystem but does not disclose the faulty policy decision or code path, and the linked Chromium issue requires permission. Exploitation requires a user to load attacker-controlled HTML; the reported consequence is cross-origin data disclosure without integrity or availability impact.
The record
- CVE
- CVE-2021-38019
- Published
- Dec 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-670, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=unspecified <96.0.4664.45
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.
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