safety Package on Python reliance on untrusted inputs in a security decision

Summaryinfo

A vulnerability was found in safety Package on Python. It has been rated as critical. This affects an unknown part. The manipulation leads to reliance on untrusted inputs in a security decision. This vulnerability is listed as CVE-2020-5252. The attack must be carried out locally. There is no available exploit.

Detailsinfo

A vulnerability was found in safety Package on Python (version unknown) and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a reliance on untrusted inputs in a security decision vulnerability. Using CWE to declare the problem leads to CWE-807. The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The command-line "safety" package for Python has a potential security issue. There are two Python characteristics that allow malicious code to “poison-pill� command-line Safety package detection routines by disguising, or obfuscating, other malicious or non-secure packages. This vulnerability is considered to be of low severity because the attack makes use of an existing Python condition, not the Safety tool itself. This can happen if: You are running Safety in a Python environment that you don’t trust. You are running Safety from the same Python environment where you have your dependencies installed. Dependency packages are being installed arbitrarily or without proper verification. Users can mitigate this issue by doing any of the following: Perform a static analysis by installing Docker and running the Safety Docker image: $ docker run --rm -it pyupio/safety check -r requirements.txt Run Safety against a static dependencies list, such as the requirements.txt file, in a separate, clean Python environment. Run Safety from a Continuous Integration pipeline. Use PyUp.io, which runs Safety in a controlled environment and checks Python for dependencies without any need to install them. Use PyUp's Online Requirements Checker.

The weakness was presented 03/23/2020 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-5252 since 01/02/2020. The exploitation is known to be difficult. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• safety Package

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion