Cross-site scripting via incomplete JavaScript escaping
Published Jan 10, 2020 · Updated Aug 6, 2024
Cross-site scripting in Spring Web MVC 3.0.0 through 3.2.1 allows remote attackers to inject browser script through escaped output. JavaScriptUtils.javaScriptEscape passes <, >, U+2028, and U+2029 through instead of encoding them for JavaScript string and HTML script-data contexts. Exploitation requires an application to apply the method to attacker-controlled text and place its result in a page viewed by another user, enabling script execution in that user's browser.
Summary
What happened
Cross-site scripting in Spring Web MVC 3.0.0 through 3.2.1 allows remote attackers to inject browser script through escaped output. JavaScriptUtils.javaScriptEscape passes <, >, U+2028, and U+2029 through instead of encoding them for JavaScript string and HTML script-data contexts. Exploitation requires an application to apply the method to attacker-controlled text and place its result in a page viewed by another user, enabling script execution in that user's browser.
The record
- CVE
- CVE-2013-6430
- Published
- Jan 10, 2020
- Updated
- Aug 6, 2024
- Vendor
- Pivotal Software
- Product
- Spring Web MVC
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=before 3.2.2
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