Stored XSS via evaluated job name
Published Nov 13, 2024 · Updated Nov 14, 2024
Stored XSS in Jenkins Authorize Project Plugin 1.7.2 and earlier allows remote authenticated users to execute JavaScript in another user's browser. The checkPasswordRequested.js code reads a job-derived URL attribute and passes it to eval() on the Authorization view without neutralizing the job name. Item/Configure permission is required, and execution occurs when another user opens the affected view, allowing the injected script to act in that user's Jenkins session.
Summary
What happened
Stored XSS in Jenkins Authorize Project Plugin 1.7.2 and earlier allows remote authenticated users to execute JavaScript in another user's browser. The checkPasswordRequested.js code reads a job-derived URL attribute and passes it to eval() on the Authorization view without neutralizing the job name. Item/Configure permission is required, and execution occurs when another user opens the affected view, allowing the injected script to act in that user's Jenkins session.
The record
- CVE
- CVE-2024-52552
- Published
- Nov 13, 2024
- Updated
- Nov 14, 2024
- Vendor
- Jenkins Project
- Product
- Authorize Project Plugin
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 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=0 <=1.7.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