<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 09:03:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-49297 — Unsafe YAML deserialization in PyDrive2</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-49297</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; iterative PyDrive2&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; iterative PyDrive2&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-49297</guid>
    </item>
    <item>
      <title>GHSA-v5f6-hjmf-9mc5 — PyDrive2's unsafe YAML deserialization in LoadSettingsFile allows arbitrary code execution</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-v5f6-hjmf-9mc5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PyDrive2&lt;/p&gt;
&lt;p&gt;### 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`.&lt;/p&gt;
&lt;p&gt;### Details
The loader being imported from the `yaml` library is `CLoader`: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L5&lt;/p&gt;
&lt;p&gt;This loader is then used to load a user supplied file: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L108-L121&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L9&lt;/p&gt;
&lt;p&gt;Reference: https://www.exploit-db.com/docs/english/47655-yaml-deserialization-attack-in-python.pdf&lt;/p&gt;
&lt;p&gt;### PoC
1. Create a malicious `settings.yaml` file:&lt;/p&gt;
&lt;p&gt;```yaml
!!python/object/new:os.system [echo poc]
```
2. Initialize a `GoogleAuth` object .
```python
from pydrive2.auth import GoogleAuth&lt;/p&gt;
&lt;p&gt;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  py…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PyDrive2&lt;/p&gt;
&lt;p&gt;### 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`.&lt;/p&gt;
&lt;p&gt;### Details
The loader being imported from the `yaml` library is `CLoader`: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L5&lt;/p&gt;
&lt;p&gt;This loader is then used to load a user supplied file: https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L108-L121&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;https://github.com/iterative/PyDrive2/blob/30c0f487c0666c0d1944ef774107359f39adc2fa/pydrive2/settings.py#L9&lt;/p&gt;
&lt;p&gt;Reference: https://www.exploit-db.com/docs/english/47655-yaml-deserialization-attack-in-python.pdf&lt;/p&gt;
&lt;p&gt;### PoC
1. Create a malicious `settings.yaml` file:&lt;/p&gt;
&lt;p&gt;```yaml
!!python/object/new:os.system [echo poc]
```
2. Initialize a `GoogleAuth` object .
```python
from pydrive2.auth import GoogleAuth&lt;/p&gt;
&lt;p&gt;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  py…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-v5f6-hjmf-9mc5</guid>
    </item>
    <item>
      <title>PYSEC-2023-291</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2023-291</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pydrive2&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pydrive2&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2023-291</guid>
    </item>
  </channel>
</rss>
