File system restriction bypass
Published Jan 10, 2023 · Updated Aug 2, 2024
An implementation flaw in Google Chrome on Windows before 109.0.5414.74 allows remote attackers to bypass file system restrictions. Google identifies the affected locus as the File System API, but the restricted issue record leaves the incorrect operation on untrusted input undisclosed. Exploitation requires a user to load a crafted HTML page; the documented consequence is unauthorized file-system access rather than disclosure or service interruption.
Summary
What happened
An implementation flaw in Google Chrome on Windows before 109.0.5414.74 allows remote attackers to bypass file system restrictions. Google identifies the affected locus as the File System API, but the restricted issue record leaves the incorrect operation on untrusted input undisclosed. Exploitation requires a user to load a crafted HTML page; the documented consequence is unauthorized file-system access rather than disclosure or service interruption.
The record
- CVE
- CVE-2023-0140
- Published
- Jan 10, 2023
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <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.
Weakness, pattern, technique
No sourced classifications are available.
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