Credential theft via unchecked form validation
Published Jan 24, 2023 · Updated Apr 2, 2025
Missing authorization in GitHub Pull Request Builder 1.42.2 and earlier allows remote authenticated users to capture Jenkins credentials. Form-validation methods accept an attacker-specified URL and credential ID without checking authorization, causing Jenkins to authenticate to the attacker’s HTTP server. Overall/Read permission and a credential ID obtained through another method are required; successful exploitation discloses the selected stored credential.
Summary
What happened
Missing authorization in GitHub Pull Request Builder 1.42.2 and earlier allows remote authenticated users to capture Jenkins credentials. Form-validation methods accept an attacker-specified URL and credential ID without checking authorization, causing Jenkins to authenticate to the attacker’s HTTP server. Overall/Read permission and a credential ID obtained through another method are required; successful exploitation discloses the selected stored credential.
The record
- CVE
- CVE-2023-24435
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- Jenkins Project
- Product
- GitHub Pull Request Builder
- Classifications
- CWE-862, T1555
- Attack vector
- network
- Privileges
- authenticated
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