Agent impersonation via reused encryption parameters
Published Jan 29, 2020 · Updated Aug 4, 2024
Authentication bypass in Jenkins weekly 2.218 and earlier and LTS 2.204.1 and earlier allows remote attackers to impersonate inbound agents. Inbound TCP Agent Protocol/3 reuses encryption parameters, letting an attacker who knows an agent name derive its connection secret. The exposed protocol and an existing agent name are required; the recovered secret authenticates an attacker-controlled agent to the controller.
Summary
What happened
Authentication bypass in Jenkins weekly 2.218 and earlier and LTS 2.204.1 and earlier allows remote attackers to impersonate inbound agents. Inbound TCP Agent Protocol/3 reuses encryption parameters, letting an attacker who knows an agent name derive its connection secret. The exposed protocol and an existing agent name are required; the recovered secret authenticates an attacker-controlled agent to the controller.
The record
- CVE
- CVE-2020-2099
- Published
- Jan 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-330, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <=2.213
- Affected versionversion=unspecified <=LTS 2.204.1
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