Authenticated outbound connections via unchecked test endpoints
Published May 11, 2021 · Updated Aug 3, 2024
Missing authorization in Jenkins Project P4 Plugin 1.11.4 and earlier allows remote authenticated users to initiate Perforce connections. The doTestConnection methods in P4PasswordImpl and P4TicketImpl accept a caller-supplied server, username, and password without checking Jenkins.ADMINISTER. Overall/Read access is sufficient, and the controller attempts the supplied credentials against the specified Perforce server.
Summary
What happened
Missing authorization in Jenkins Project P4 Plugin 1.11.4 and earlier allows remote authenticated users to initiate Perforce connections. The doTestConnection methods in P4PasswordImpl and P4TicketImpl accept a caller-supplied server, username, and password without checking Jenkins.ADMINISTER. Overall/Read access is sufficient, and the controller attempts the supplied credentials against the specified Perforce server.
The record
- CVE
- CVE-2021-21654
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- P4 Plugin
- Classifications
- CWE-862, T1046
- Attack vector
- network
- Privileges
- authenticated
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.
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