Safe Browsing warning bypass via malicious file
Published Nov 29, 2022 · Updated Aug 3, 2024
Insufficient Safe Browsing policy enforcement in Google Chrome before 108.0.5359.71 allows remote attackers to bypass warnings with a malicious file. The public record identifies the Safe Browsing component but does not disclose which policy check mishandles the file or why the warning is suppressed. A user must interact with the malicious file; the demonstrated consequence is loss of the browser's warning, not direct code execution or data disclosure.
Summary
What happened
Insufficient Safe Browsing policy enforcement in Google Chrome before 108.0.5359.71 allows remote attackers to bypass warnings with a malicious file. The public record identifies the Safe Browsing component but does not disclose which policy check mishandles the file or why the warning is suppressed. A user must interact with the malicious file; the demonstrated consequence is loss of the browser's warning, not direct code execution or data disclosure.
The record
- CVE
- CVE-2022-4195
- Published
- Nov 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <108.0.5359.71
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