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.
Metrics
Affected Vendors & Products
References
History
Tue, 04 Mar 2025 03:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Mon, 03 Mar 2025 16:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Wed, 26 Feb 2025 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | picklescan - Security scanning bypass via 'pip main' | |
Weaknesses | CWE-184 | |
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: Sonatype
Published:
Updated: 2025-03-03T15:58:37.163Z
Reserved: 2025-02-26T12:08:39.343Z
Link: CVE-2025-1716

Updated: 2025-02-26T15:49:30.635Z

Status : Received
Published: 2025-02-26T15:15:24.653
Modified: 2025-03-03T16:15:39.520
Link: CVE-2025-1716

No data.