Code execution via unsafe YAML configuration loading
Published Sep 10, 2021 · Updated Aug 4, 2024
Unsafe YAML deserialization in Meta Platforms ParlAI before 1.1.0 allows attackers to execute code through a crafted local configuration file. The parse_configuration_file and model-chat blueprint helpers pass YAML contents to yaml.load with FullLoader or the default loader instead of SafeLoader. Exploitation requires control of a local configuration that a chat-service or crowdsourcing workflow later loads, after which code runs with that process's privileges.
Summary
What happened
Unsafe YAML deserialization in Meta Platforms ParlAI before 1.1.0 allows attackers to execute code through a crafted local configuration file. The parse_configuration_file and model-chat blueprint helpers pass YAML contents to yaml.load with FullLoader or the default loader instead of SafeLoader. Exploitation requires control of a local configuration that a chat-service or crowdsourcing workflow later loads, after which code runs with that process's privileges.
The record
- CVE
- CVE-2021-39207
- Published
- Sep 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Meta Platforms, Inc.
- Product
- ParlAI
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 10, 2021CVE 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=< 1.1.0
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