Local code execution via unsafe YAML loading
Published Oct 4, 2021 · Updated Aug 3, 2024
Code injection in Google SLO Generator 2.0.0 and earlier allows local users to execute code through a crafted YAML migration file. The migrate command passes backend configuration to PyYAML's unsafe yaml.Loader, which constructs Python object tags that invoke os.system. Local access sufficient to run the CLI and select the crafted file is required, and resulting commands execute with the SLO Generator process's privileges.
Summary
What happened
Code injection in Google SLO Generator 2.0.0 and earlier allows local users to execute code through a crafted YAML migration file. The migrate command passes backend configuration to PyYAML's unsafe yaml.Loader, which constructs Python object tags that invoke os.system. Local access sufficient to run the CLI and select the crafted file is required, and resulting commands execute with the SLO Generator process's privileges.
The record
- CVE
- CVE-2021-22557
- Published
- Oct 4, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- SLO Generator
- Classifications
- CWE-94, CWE-78, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 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 <=2.0.0
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
- Upstream yaml.Loader migration proof of conceptproof of concept · demonstrated
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