Attacker-directed outbound connection via CSRF form validation
Published Feb 15, 2023 · Updated Mar 19, 2025
CSRF in Jenkins Azure Credentials Plugin 253.v887e0f9e898b and earlier allows remote attackers to direct Jenkins to an attacker-controlled server. The doVerifyConfiguration methods accepted endpoint parameters without POST enforcement or authorization, then validated Azure credentials against those endpoints. Exploitation requires a user with Overall/Read permission to visit a crafted page; the bounded effect is an outbound connection from the Jenkins controller.
Summary
What happened
CSRF in Jenkins Azure Credentials Plugin 253.v887e0f9e898b and earlier allows remote attackers to direct Jenkins to an attacker-controlled server. The doVerifyConfiguration methods accepted endpoint parameters without POST enforcement or authorization, then validated Azure credentials against those endpoints. Exploitation requires a user with Overall/Read permission to visit a crafted page; the bounded effect is an outbound connection from the Jenkins controller.
The record
- CVE
- CVE-2023-25767
- Published
- Feb 15, 2023
- Updated
- Mar 19, 2025
- Vendor
- Jenkins Project
- Product
- Azure Credentials
- Classifications
- CWE-352, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 15, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 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 <=253.v887e0f9e898b
What conditions does exploitation require?
What is affected?
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