Arbitrary code execution via unsafe YAML loader
Published Dec 5, 2023 · Updated Feb 13, 2025
Unsafe YAML deserialization in Iterative PyDrive2 before 1.16.2 and PyDrive2 1.17.0 allows local users to execute arbitrary code. LoadSettingsFile passes settings.yaml content to PyYAML's unsafe CLoader or Loader, allowing Python object tags to invoke code during parsing. Exploitation requires a crafted settings file in the process directory or an explicit LoadSettingsFile call, followed by application initialization, and code runs with the process privileges.
Summary
What happened
Unsafe YAML deserialization in Iterative PyDrive2 before 1.16.2 and PyDrive2 1.17.0 allows local users to execute arbitrary code. LoadSettingsFile passes settings.yaml content to PyYAML's unsafe CLoader or Loader, allowing Python object tags to invoke code during parsing. Exploitation requires a crafted settings file in the process directory or an explicit LoadSettingsFile call, followed by application initialization, and code runs with the process privileges.
The record
- CVE
- CVE-2023-49297
- Published
- Dec 5, 2023
- Updated
- Feb 13, 2025
- Vendor
- Iterative
- Product
- PyDrive2
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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.16.2
- Affected versionversion== 1.17.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
- GitHub advisory settings.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