Credential capture via GET-enabled form validation
Published Feb 15, 2022 · Updated Aug 3, 2024
Cross-site request forgery in Jenkins SWAMP Plugin 1.2.6 and earlier allows remote attackers to expose stored credentials via a crafted GET request. The form-validation method accepts GET requests and uses an attacker-supplied server URL and credential ID to initiate an outbound connection. A logged-in user must load attacker-controlled content, and successful credential capture requires knowledge of a stored credential ID.
Summary
What happened
Cross-site request forgery in Jenkins SWAMP Plugin 1.2.6 and earlier allows remote attackers to expose stored credentials via a crafted GET request. The form-validation method accepts GET requests and uses an attacker-supplied server URL and credential ID to initiate an outbound connection. A logged-in user must load attacker-controlled content, and successful credential capture requires knowledge of a stored credential ID.
The record
- CVE
- CVE-2022-25212
- Published
- Feb 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins SWAMP Plugin
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 15, 2022CVE 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 <=1.2.6
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