Credential capture via CSRF-enabled connection endpoints
Published Aug 21, 2023 · Updated Oct 1, 2024
CSRF in Jenkins Fortify Plugin 22.1.38 and earlier allows remote authenticated users to capture stored credentials through HTTP endpoints. Several Stapler form-validation and refresh endpoints accept non-POST requests, then use supplied URLs and stored credential IDs for outbound connections. Overall/Read permission and a valid credential ID are required, and the consequence is disclosure of the selected Jenkins credential.
Summary
What happened
CSRF in Jenkins Fortify Plugin 22.1.38 and earlier allows remote authenticated users to capture stored credentials through HTTP endpoints. Several Stapler form-validation and refresh endpoints accept non-POST requests, then use supplied URLs and stored credential IDs for outbound connections. Overall/Read permission and a valid credential ID are required, and the consequence is disclosure of the selected Jenkins credential.
The record
- CVE
- CVE-2023-4301
- Published
- Aug 21, 2023
- Updated
- Oct 1, 2024
- Vendor
- Jenkins Project
- Product
- Fortify Jenkins Plugin
- Classifications
- CWE-352, T1555
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2023CVE publishedPublication date reported by the CVE source.
- Oct 1, 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 <=22.1.38
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