Code execution via fact-controlled module selection
Published Mar 16, 2020 · Updated Aug 4, 2024
Argument injection in Red Hat Ansible allows local users to execute code on managed nodes via attacker-controlled module-selection facts. The package.py and service.py action plugins trust ansible_facts values for pkg_mgr or service_mgr as the module name when use is omitted, including an attacker-chosen collection path. Exploitation requires control of facts before an operator runs a package or service task without use, after which the selected payload runs on the managed node.
Summary
What happened
Argument injection in Red Hat Ansible allows local users to execute code on managed nodes via attacker-controlled module-selection facts. The package.py and service.py action plugins trust ansible_facts values for pkg_mgr or service_mgr as the module name when use is omitted, including an attacker-chosen collection path. Exploitation requires control of facts before an operator runs a package or service task without use, after which the selected payload runs on the managed node.
The record
- CVE
- CVE-2020-1738
- Published
- Mar 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Ansible
- Classifications
- CWE-88, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 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=2.7.x, 2.8.x, 2.9.x
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