Code execution via crafted workflow YAML
Published Feb 15, 2021 · Updated Sep 16, 2024
Deserialization in Qlib before 0.7.0 allows attackers to execute arbitrary Python code through a crafted workflow YAML file. The published proof of concept invokes qlib.workflow.cli.workflow with a YAML object tag, while the corrective commit replaces yaml.load with yaml.safe_load in qlib/workflow/cli.py. Execution requires a local process to load the attacker-controlled file; Snyk now states that the advisory does not affect qlib and deems it not a vulnerability.
Summary
What happened
Deserialization in Qlib before 0.7.0 allows attackers to execute arbitrary Python code through a crafted workflow YAML file. The published proof of concept invokes qlib.workflow.cli.workflow with a YAML object tag, while the corrective commit replaces yaml.load with yaml.safe_load in qlib/workflow/cli.py. Execution requires a local process to load the attacker-controlled file; Snyk now states that the advisory does not affect qlib and deems it not a vulnerability.
The record
- CVE
- CVE-2021-23338
- Published
- Feb 15, 2021
- Updated
- Sep 16, 2024
- Vendor
- Microsoft
- Product
- Qlib
- Classifications
- CWE-502, T1059.006
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 15, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=0 <unspecified
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.
Public exploit references
- Huntr workflow YAML 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