CVE-2023-49297: PyDrive2 PyDrive2's Unsafe YAML Deserialization Vulnerability

LOW
Advisory Identifier: GHSA-v5f6-hjmf-9mc5
CVSS 3.3
CWE-502
Published
Advisory Summary

CVE-2023-49297 is a LOW (CVSS 3.3) pydrive2's unsafe yaml deserialization vulnerability (CWE-502: Deserialization of Untrusted Data) affecting PyDrive2 libraries in the PyPI ecosystem. The issue involves pydrive2's unsafe yaml deserialization in loadsettingsfile allows arbitrary code execution. Remediation is available by upgrading affected packages to version 1.16.2.

CVE-2023-49297 at a Glance

CVE Identifier CVE-2023-49297
GHSA Identifier GHSA-v5f6-hjmf-9mc5
Severity LOW
CVSS v3.1 Base Score 3.3
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product PyDrive2
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 3.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2023-49297

To remediate this vulnerability, upgrade all affected PyDrive2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

PyDrive2 fixed: Latest secure release
pip install PyDrive2>=Latest secure release
PyDrive2 fixed: 1.16.2
pip install PyDrive2>=1.16.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show PyDrive2

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2023-49297, inspect your installed packages using pip:

pip show PyDrive2

Analyze the terminal output to locate any version of PyDrive2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.16.2), your application is affected.

Note: The pip show PyDrive2 command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In PyDrive2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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. https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L9 Reference: https://www.exploit-db.com/docs/english/47655-yaml-deserialization-attack-in-python.pdf ### PoC 1. Create a malicious `settings.yaml` file: ```yaml !!python/object/new:os.system [echo poc] ``` 2. Initialize a `GoogleAuth` object . ```python from pydrive2.auth import GoogleAuth gauth = GoogleAuth() ``` 3. 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.

CVE-2023-49297 Affected PyDrive2 Versions

2 component(s)
Fixed Versions:
1.16.2
Product / Package Ecosystem Affected Versions Fixed Version
PyDrive2
PyPI
1.17.0
All 1 versions
1.17.0
None specified
PyDrive2
PyPI
< 1.16.2
1.16.2

References

Frequently Asked Questions

What is CVE-2023-49297?
CVE-2023-49297 is a security vulnerability in PyDrive2 involving PyDrive2's unsafe YAML deserialization in LoadSettingsFile allows arbitrary code execution under CWE-502: Deserialization of Untrusted Data.
Which PyDrive2 versions are affected?
Affected versions include releases prior to 1.16.2 across affected packages: PyDrive2.
What version fixes CVE-2023-49297?
Upgrading to 1.16.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is PyDrive2 affected?
Yes, PyDrive2 is affected in releases prior to Latest secure release, 1.16.2. Upgrade your dependency to Latest secure release, 1.16.2 or later.
What is the CVSS score of CVE-2023-49297?
CVE-2023-49297 has a CVSS v3.1 base score of 3.3 (LOW) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2023-49297?
CVE-2023-49297 is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check PyPI dependencies for CVE-2023-49297?
Run the dependency tree command: 'pip show PyDrive2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v5f6-hjmf-9mc5",
  "modified" : "2024-11-22T20:20:57Z",
  "published" : "2023-12-05T23:43:07Z",
  "aliases" : [ "CVE-2023-49297" ],
  "summary" : "PyDrive2's unsafe YAML deserialization in LoadSettingsFile allows arbitrary code execution",
  "details" : "### 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. ",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "PyDrive2"
    },
    "versions" : [ "1.17.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "PyDrive2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.16.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/iterative/PyDrive2/security/advisories/GHSA-v5f6-hjmf-9mc5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-49297"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/iterative/PyDrive2/commit/c57355dc2033ad90b7050d681b2c3ba548ff0004"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/iterative/PyDrive2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/pydrive2/PYSEC-2023-291.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CYR5SJKOFSSXFV3E3D2SLXBUBA5WMJJG"
  }, {
    "type" : "WEB",
    "url" : "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/K34YWTDKBAYWZPOAKBYDM72WIFL5CAYW"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-12-05T23:43:07Z",
    "nvd_published_at" : "2023-12-05T21:15:07Z"
  }
}