iterative PyDrive2 1.17.0

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:iterative:pydrive2:1.17.0:*:*:*:*:*:*:*

part: a version: 1.17.0 update: *

VendorIterative (ef8f16b6-1e3e-5fe4-8455-420e61a2e6ad)
ProductPydrive2 (755dd487-380f-56c9-b78e-2c1e7171863b)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/iterative/pydrive2 purl2cpe 2026-06-01 10:14:40.178026
pkg:pypi/pydrive2 purl2cpe 2026-06-01 10:14:40.178028
pkg:rpm/fedora/pydrive2 purl2cpe 2026-06-01 10:14:40.178029
pkg:rpm/opensuse/python-pydrive2 purl2cpe 2026-06-01 10:14:40.178031

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-49297 vulnerable 2026-06-08 06:14:28.990765 Unsafe YAML deserialization in PyDrive2
LOW (3.3)
PyDrive2 is a wrapper library of google-api-python-client that simplifies many common Google Drive API V2 tasks. 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`. 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. This vulnerability does not require the file to be directly loaded through the code, only present. This issue has been addressed in commit `c57355dc` which is included in release version `1.16.2`. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Published: 2023-12-05T20:51:24.143Z
Updated: 2025-02-13T17:18:41.420Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.