UTC
Medium

fickling's `platform` module subprocess invocation evades `check_safety()` with `LIKELY_SAFE`

GHSA-5cxw-w2xg-2m8h · published 2026-03-13

Severity
Medium
CVSS score
6.9
Chance of exploitation (EPSS)
No CVE
Fixed in
0.1.10
What it is

False-negative verdict: checksafety() returns LIKELYSAFE with zero findings for a pickle that invokes a subprocess with attacker-controlled arguments. Subprocess invocation: platform.syscmdfile calls command reads file headers and returns type information, enabling file existence and type probing. File read: platform.libc_ver opens and reads chunks of an attacker-specified file path.

What to do

Upgrade fickling to 0.1.10 or later.

Affected
PackageRegistryAffectedFixed in
ficklingPyPI<= 0.1.90.1.10

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].