Credential theft via CSRF-enabled validation requests
Published Jan 24, 2023 · Updated Apr 2, 2025
Cross-site request forgery in Jenkins GitHub Pull Request Builder Plugin 1.42.2 and earlier allows attackers to capture stored credentials. Form-validation methods accept non-POST requests without permission checks and connect to an attacker-controlled URL using a supplied credentials ID. Exploitation requires user interaction and a valid credentials ID obtained separately, and it exposes the associated Jenkins credential to the remote server.
Summary
What happened
Cross-site request forgery in Jenkins GitHub Pull Request Builder Plugin 1.42.2 and earlier allows attackers to capture stored credentials. Form-validation methods accept non-POST requests without permission checks and connect to an attacker-controlled URL using a supplied credentials ID. Exploitation requires user interaction and a valid credentials ID obtained separately, and it exposes the associated Jenkins credential to the remote server.
The record
- CVE
- CVE-2023-24434
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- Jenkins Project
- Product
- GitHub Pull Request Builder
- Classifications
- CWE-352, T1187
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 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.42.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.
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