Noexec restriction bypass via malicious file handling
Published Jan 8, 2021 · Updated Aug 4, 2024
Filesystem policy bypass in Google Chrome on ChromeOS before 87.0.4280.66 allows remote attackers to bypass noexec via a malicious file. Google identifies an inappropriate implementation in the filesystem component but has not disclosed the faulty operation performed on the file. Exploitation requires prior compromise of the browser process and weakens the protection that prevents downloaded code from executing in writable locations.
Summary
What happened
Filesystem policy bypass in Google Chrome on ChromeOS before 87.0.4280.66 allows remote attackers to bypass noexec via a malicious file. Google identifies an inappropriate implementation in the filesystem component but has not disclosed the faulty operation performed on the file. Exploitation requires prior compromise of the browser process and weakens the protection that prevents downloaded code from executing in writable locations.
The record
- CVE
- CVE-2020-16019
- Published
- Jan 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 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 <87.0.4280.66
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