Stored XSS via unescaped script names
Published Nov 12, 2021 · Updated Aug 3, 2024
Stored XSS in Jenkins Project Scriptler 3.3 and earlier allows remote authenticated users to execute JavaScript in a victim's browser. The script-deletion confirmation view inserts an attacker-controlled script name into HTML without escaping it. Exploitation requires permission to create a Scriptler script and a victim to open its deletion confirmation; the injected code runs with that victim's Jenkins web privileges.
Summary
What happened
Stored XSS in Jenkins Project Scriptler 3.3 and earlier allows remote authenticated users to execute JavaScript in a victim's browser. The script-deletion confirmation view inserts an attacker-controlled script name into HTML without escaping it. Exploitation requires permission to create a Scriptler script and a victim to open its deletion confirmation; the injected code runs with that victim's Jenkins web privileges.
The record
- CVE
- CVE-2021-21700
- Published
- Nov 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Scriptler
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2021CVE 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 <=3.3
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