Unauthorized outbound connections via CSRF-prone test endpoints
Published May 11, 2021 · Updated Aug 3, 2024
CSRF in Jenkins P4 Plugin 1.11.4 and earlier allows remote attackers to make Jenkins connect to an attacker-controlled Perforce server. Multiple connection-test HTTP endpoints accept non-POST requests and use attacker-supplied server, username, and password values. Exploitation requires a Jenkins user to load a crafted request and directs a server-side connection without exposing stored Jenkins credentials.
Summary
What happened
CSRF in Jenkins P4 Plugin 1.11.4 and earlier allows remote attackers to make Jenkins connect to an attacker-controlled Perforce server. Multiple connection-test HTTP endpoints accept non-POST requests and use attacker-supplied server, username, and password values. Exploitation requires a Jenkins user to load a crafted request and directs a server-side connection without exposing stored Jenkins credentials.
The record
- CVE
- CVE-2021-21655
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- P4 Plugin
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <=1.11.4
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