Authenticated command execution via untrusted play path
Published Jun 3, 2020 · Updated Aug 4, 2024
OS command injection in Jenkins Play Framework Plugin 1.0.2 and earlier allows remote authenticated users to execute commands via a form-validation endpoint. The endpoint runs the play command using a path supplied by the user to validate an input file, without neutralizing command metacharacters. Access requires the ability to store a file on the Jenkins controller, such as by archiving an artifact, and successful exploitation can compromise controller confidentiality, integrity, and availability.
Summary
What happened
OS command injection in Jenkins Play Framework Plugin 1.0.2 and earlier allows remote authenticated users to execute commands via a form-validation endpoint. The endpoint runs the play command using a path supplied by the user to validate an input file, without neutralizing command metacharacters. Access requires the ability to store a file on the Jenkins controller, such as by archiving an artifact, and successful exploitation can compromise controller confidentiality, integrity, and availability.
The record
- CVE
- CVE-2020-2200
- Published
- Jun 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Play Framework Plugin
- Classifications
- CWE-78, T1059
- 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 <=1.0.2
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