Skip to content

Commit

Permalink
Latest data: Sat Dec 9 08:04:51 UTC 2023
Browse files Browse the repository at this point in the history
  • Loading branch information
github.actions committed Dec 9, 2023
1 parent 98fb4fa commit ec56118
Show file tree
Hide file tree
Showing 8 changed files with 40 additions and 843 deletions.
152 changes: 0 additions & 152 deletions audits/dvc-requirements.audit.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -119,157 +119,5 @@
]
}
]
},
{
"package": {
"name": "pydrive2",
"version": "1.17.0",
"ecosystem": "PyPI"
},
"vulnerabilities": [
{
"modified": "2023-12-05T23:58:16Z",
"published": "2023-12-05T23:43:07Z",
"schema_version": "1.6.0",
"id": "GHSA-v5f6-hjmf-9mc5",
"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. ",
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "pydrive2",
"purl": "pkg:pypi/pydrive2"
},
"versions": [
"1.17.0"
],
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/12/GHSA-v5f6-hjmf-9mc5/GHSA-v5f6-hjmf-9mc5.json"
}
},
{
"package": {
"ecosystem": "PyPI",
"name": "pydrive2",
"purl": "pkg:pypi/pydrive2"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.16.2"
}
]
}
],
"versions": [
"0.14.0",
"1.10.0",
"1.10.1",
"1.10.2",
"1.11.0",
"1.11.1",
"1.11.2",
"1.12.0",
"1.12.1",
"1.13.0",
"1.14.0",
"1.15.0",
"1.15.1",
"1.15.2",
"1.15.3",
"1.15.4",
"1.16.0",
"1.16.1",
"1.4.0",
"1.4.1",
"1.4.10",
"1.4.11",
"1.4.12",
"1.4.13",
"1.4.14",
"1.4.2",
"1.4.4",
"1.4.5",
"1.4.6",
"1.4.7",
"1.4.8",
"1.4.9",
"1.6.0",
"1.6.1",
"1.6.2",
"1.6.3",
"1.7.0",
"1.7.2",
"1.7.3",
"1.8.0",
"1.8.1",
"1.8.2",
"1.8.3",
"1.9.0",
"1.9.1",
"1.9.2",
"1.9.3",
"1.9.4"
],
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/12/GHSA-v5f6-hjmf-9mc5/GHSA-v5f6-hjmf-9mc5.json"
}
}
],
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N"
}
],
"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"
}
],
"database_specific": {
"cwe_ids": [
"CWE-502"
],
"github_reviewed": true,
"github_reviewed_at": "2023-12-05T23:43:07Z",
"nvd_published_at": "2023-12-05T21:15:07Z",
"severity": "LOW"
}
}
],
"groups": [
{
"ids": [
"GHSA-v5f6-hjmf-9mc5"
],
"aliases": [
"CVE-2023-49297",
"GHSA-v5f6-hjmf-9mc5"
]
}
]
}
]
234 changes: 0 additions & 234 deletions audits/jupyterlab-requirements.audit.json
View file

This file was deleted.

Loading

0 comments on commit ec56118

Please sign in to comment.