Stored credential theft via CSRF-triggered outbound requests
Published Mar 30, 2021 · Updated Nov 19, 2024
CSRF in Jenkins OWASP Dependency-Track Plugin 3.1.0 and earlier allows remote attackers to capture stored credentials via crafted requests. Several HTTP endpoints accept non-POST requests and connect to an attacker-specified URL with either a supplied credential ID or the configured global credential. Exploitation requires a Jenkins user's browser to submit the request; the outbound connection exposes Secret text credentials to the attacker-controlled service.
Summary
What happened
CSRF in Jenkins OWASP Dependency-Track Plugin 3.1.0 and earlier allows remote attackers to capture stored credentials via crafted requests. Several HTTP endpoints accept non-POST requests and connect to an attacker-specified URL with either a supplied credential ID or the configured global credential. Exploitation requires a Jenkins user's browser to submit the request; the outbound connection exposes Secret text credentials to the attacker-controlled service.
The record
- CVE
- CVE-2021-21633
- Published
- Mar 30, 2021
- Updated
- Nov 19, 2024
- Vendor
- Jenkins Project
- Product
- OWASP Dependency-Track Jenkins Plugin
- Classifications
- CWE-352, T1555
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 30, 2021CVE publishedPublication date reported by the CVE source.
- Nov 19, 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=1.1.0 <unspecified
- Affected versionversion=unspecified <=3.1.0
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