Browser script execution via unescaped S3 names
Published Feb 13, 2020 · Updated Aug 5, 2024
Cross-site scripting in AWS JavaScript S3 Explorer v2 alpha before 2019-08-02 allows attackers to execute script in a visitor's browser. explorer.js inserts S3 object keys and path components into generated anchor text and data-s3key attributes without HTML escaping. Exploitation requires an attacker-controlled object or prefix name in a bucket the victim browses and user interaction that renders the malicious name.
Summary
What happened
Cross-site scripting in AWS JavaScript S3 Explorer v2 alpha before 2019-08-02 allows attackers to execute script in a visitor's browser. explorer.js inserts S3 object keys and path components into generated anchor text and data-s3key attributes without HTML escaping. Exploitation requires an attacker-controlled object or prefix name in a bucket the victim browses and user interaction that renders the malicious name.
The record
- CVE
- CVE-2019-14652
- Published
- Feb 13, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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