XSS prevention bypass via malicious file
Published Nov 1, 2023 · Updated Feb 13, 2025
Cross-site scripting bypass in Google Chrome before 119.0.6045.105 allows remote attackers to evade XSS protections via a malicious file. Google has not published which Payments code path mishandles the file or how the bypass occurs. Exploitation requires a user to open the malicious file, after which attacker-controlled script can cross an origin boundary to read or alter data.
Summary
What happened
Cross-site scripting bypass in Google Chrome before 119.0.6045.105 allows remote attackers to evade XSS protections via a malicious file. Google has not published which Payments code path mishandles the file or how the bypass occurs. Exploitation requires a user to open the malicious file, after which attacker-controlled script can cross an origin boundary to read or alter data.
The record
- CVE
- CVE-2023-5480
- Published
- Nov 1, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-79, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=119.0.6045.105 <119.0.6045.105
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