Agent label modification via CSRF-enabled GET endpoints
Published Jun 3, 2020 · Updated Aug 4, 2024
Cross-site request forgery in Jenkins Swarm Plugin 3.20 and earlier allows remote authenticated users to alter labels on any agent. The doAddSlaveLabels and doRemoveSlaveLabels endpoints accept state-changing requests without enforcing POST, allowing forged requests to reach label updates. Agent/Create permission is sufficient to obtain the global Swarm secret required by the endpoints; successful requests alter agent scheduling metadata.
Summary
What happened
Cross-site request forgery in Jenkins Swarm Plugin 3.20 and earlier allows remote authenticated users to alter labels on any agent. The doAddSlaveLabels and doRemoveSlaveLabels endpoints accept state-changing requests without enforcing POST, allowing forged requests to reach label updates. Agent/Create permission is sufficient to obtain the global Swarm secret required by the endpoints; successful requests alter agent scheduling metadata.
The record
- CVE
- CVE-2020-2192
- Published
- Jun 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Swarm Plugin
- Classifications
- CWE-352, CAPEC-62, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 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 <=3.20
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.
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