CVE-2020-5252
Last modified
CVE-2020-5252 is a medium-severity vulnerability rated 4.1/10 on the CVSS scale. 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. EPSS estimates a 0.37% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Pyup | Safety | <= 1.8.6 |
References
- https://github.com/akoumjian/python-safety-vulnProduct, Third Party Advisory
- https://github.com/pyupio/safety/security/advisories/GHSA-7q25-qrjw-6fg2Mitigation, Third Party Advisory
- https://pyup.io/posts/patched-vulnerability/Vendor Advisory
- https://github.com/akoumjian/python-safety-vulnProduct, Third Party Advisory
- https://github.com/pyupio/safety/security/advisories/GHSA-7q25-qrjw-6fg2Mitigation, Third Party Advisory
- https://pyup.io/posts/patched-vulnerability/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-5252?
How severe is CVE-2020-5252?
How do I fix CVE-2020-5252?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-5246Traccar GPS Tracking System before version 4.9 has a LDAP in…6.5
- CVE-2020-5247In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an appl…7.5
- CVE-2020-5248GLPI before before version 9.4.6 has a vulnerability involvi…5.3
- CVE-2020-5249In Puma (RubyGem) before 4.3.3 and 3.12.4, if an application…6.5
- CVE-2020-5250In PrestaShop before version 1.7.6.4, when a customer edits …6.3
- CVE-2020-5251In parser-server before version 4.1.0, you can fetch all the…5.3
- CVE-2020-5253NetHack before version 3.6.0 allowed malicious use of escapi…9.8
- CVE-2020-5254In NetHack before 3.6.6, some out-of-bound values for the hi…8.1
- CVE-2020-5255In Symfony before versions 4.4.7 and 5.0.7, when a `Response…4.3
- CVE-2020-5256BookStack before version 0.25.5 has a vulnerability where a …8.8
- CVE-2020-5257In Administrate (rubygem) before version 0.13.0, when sortin…8.1
- CVE-2020-5258In affected versions of dojo (NPM package), the deepCopy met…7.7
Are you affected by CVE-2020-5252?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
