Advisory

GHSA-7q25-qrjw-6fg2

Also known as: CVE-2020-5252, PYSEC-2020-101

Summary

Malicious package may avoid detection in python auditing

Details

Python Auditing Vulnerability

Demonstrates how a malicious package can insert a load-time poison pill to avoid detection by tools like Safety.

Tools that are designed to find vulnerable packages can not ever run in the same python environment that they are trying to protect.

Usage

Install safety, insecure-package, and this package with pip in the same python environment. Order doesn't matter.

  1. pip install safety
  2. pip install insecure-package
  3. pip install dist/malicious-0.1-py3-none-any.whl

Run the check

  1. safety check

You should see both Running my modified safety.check and that insecure-package is not listed in the results!

How it Works

Everything in Python is mutable. The trick is getting some code to run at interpreter load time in order to do some patching.

  1. When you install this package, the setup.py settings installs a malicious.pth file to your site-packages directory.
  2. The malicious.pth file gets loaded anytime Python starts, which in turn imports our malicious package.
  3. The malicious/__init__.py patches the safety library with a custom function to avoid detection.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-03-24 15:07 UTC
Modified
2026-07-08 06:28 UTC

Affected packages and fixes

safety

PyPI · All systems

Affected

  • introduced 0, fixed 1.9.0 (ecosystem)

Fixed versions

1.9.0

Fix

  • Fixed version 1.9.0
    pip install --upgrade safety==1.9.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences