pysec-2025-18
Vulnerability from pysec
Published
2025-02-26 15:15
Modified
2025-04-09 17:27
Details
picklescan before 0.0.21 does not treat 'pip' as an unsafe global. An attacker could craft a malicious model that uses Pickle to pull in a malicious PyPI package (hosted, for example, on pypi.org or GitHub) via pip.main()
. Because pip is not a restricted global, the model, when scanned with picklescan, would pass security checks and appear to be safe, when it could instead prove to be problematic.
Aliases
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "picklescan", "purl": "pkg:pypi/picklescan" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "78ce704227c51f070c0c5fb4b466d92c62a7aa3d" } ], "repo": "https://github.com/mmaitre314/picklescan", "type": "GIT" }, { "events": [ { "introduced": "0" }, { "fixed": "0.0.21" } ], "type": "ECOSYSTEM" } ], "versions": [ "0.0.1", "0.0.10", "0.0.11", "0.0.12", "0.0.13", "0.0.14", "0.0.15", "0.0.16", "0.0.17", "0.0.18", "0.0.19", "0.0.2", "0.0.20", "0.0.3", "0.0.4", "0.0.5", "0.0.6", "0.0.7", "0.0.8", "0.0.9" ] } ], "aliases": [ "CVE-2025-1716", "GHSA-655q-fx9r-782v" ], "details": "picklescan before 0.0.21 does not treat \u0027pip\u0027 as an unsafe global. An attacker could craft a malicious model that uses Pickle to pull in a malicious PyPI package (hosted, for example, on pypi.org or GitHub) via `pip.main()`. Because pip is not a restricted global, the model, when scanned with picklescan, would pass security checks and appear to be safe, when it could instead prove to be problematic.", "id": "PYSEC-2025-18", "modified": "2025-04-09T17:27:26.867210+00:00", "published": "2025-02-26T15:15:24+00:00", "references": [ { "type": "ADVISORY", "url": "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-655q-fx9r-782v" }, { "type": "FIX", "url": "https://github.com/mmaitre314/picklescan/commit/78ce704227c51f070c0c5fb4b466d92c62a7aa3d" }, { "type": "WEB", "url": "https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-1716" } ] }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.