Stored credential disclosure via GET-enabled form validation
Published Sep 21, 2022 · Updated May 27, 2025
Cross-site request forgery in Jenkins Project SCM HttpClient Plugin 1.5 and earlier allows remote authenticated users to capture stored credentials. A form-validation method accepts GET requests and connects to an attacker-specified HTTP server with an attacker-supplied Jenkins credentials ID. Overall/Read permission and a credentials ID obtained through another method are required, and successful exploitation discloses the corresponding stored secret.
Summary
What happened
Cross-site request forgery in Jenkins Project SCM HttpClient Plugin 1.5 and earlier allows remote authenticated users to capture stored credentials. A form-validation method accepts GET requests and connects to an attacker-specified HTTP server with an attacker-supplied Jenkins credentials ID. Overall/Read permission and a credentials ID obtained through another method are required, and successful exploitation discloses the corresponding stored secret.
The record
- CVE
- CVE-2022-41249
- Published
- Sep 21, 2022
- Updated
- May 27, 2025
- Vendor
- Jenkins Project
- Product
- SCM HttpClient Plugin
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2022CVE publishedPublication date reported by the CVE source.
- May 27, 2025Record 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.5
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