Local-file disclosure via DevTools policy failure
Published Jul 28, 2022 · Updated Jun 2, 2026
Insufficient policy enforcement in Google Chrome DevTools before 103.0.5060.53 allows attackers to read sensitive local files on Windows. Public vendor material identifies DevTools as the affected locus but does not disclose the failed policy check, code path, or improper operation. Exploitation requires a user to install a malicious extension and interact with a crafted HTML page; the reported consequence is local-file disclosure only.
Summary
What happened
Insufficient policy enforcement in Google Chrome DevTools before 103.0.5060.53 allows attackers to read sensitive local files on Windows. Public vendor material identifies DevTools as the affected locus but does not disclose the failed policy check, code path, or improper operation. Exploitation requires a user to install a malicious extension and interact with a crafted HTML page; the reported consequence is local-file disclosure only.
The record
- CVE
- CVE-2022-2160
- Published
- Jul 28, 2022
- Updated
- Jun 2, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-362, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2022CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record 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 <103.0.5060.53
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