admin/cvelist
1
0
Fork 0
mirror of https://github.com/CVEProject/cvelist.git synced 2025-05-05 10:18:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

"-Synchronized-Data."

Browse Source
This commit is contained in:
CVE Team 2020-03-24 00:01:17 +00:00
parent 513d6a1211
commit 6de5777b80
No known key found for this signature in database
GPG Key ID: 5708902F06FEF743
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
2020/5xxx/CVE-2020-5252.json
View File

@ -35,7 +35,7 @@
"description_data": [
{
"lang": "eng",
"value": "The command-line \"safety\" package for Python has a potential security issue.\n\nThere 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.\n\nThis vulnerability is considered to be of low severity because the attack makes use of an existing Python condition, not the Safety tool itself.\n\nThis can happen if:\n\nYou are running Safety in a Python environment that you don’t trust.\nYou are running Safety from the same Python environment where you have your dependencies installed.\nDependency packages are being installed arbitrarily or without proper verification.\n\nUsers can mitigate this issue by doing any of the following:\n\nPerform a static analysis by installing Docker and running the Safety Docker image: $ docker run --rm -it pyupio/safety check -r requirements.txt\n\nRun Safety against a static dependencies list, such as the requirements.txt file, in a separate, clean Python environment.\n\nRun Safety from a Continuous Integration pipeline.\n\nUse PyUp.io, which runs Safety in a controlled environment and checks Python for dependencies without any need to install them.\n\nUse PyUp's Online Requirements Checker."
"value": "The command-line \"safety\" package for Python has a potential security issue. There are two Python characteristics that allow malicious code to \u201cpoison-pill\u201d 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\u2019t 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."
}
]
},