Pip vulnerabilities
Published CVEs affecting Pip products: 108 record(s), with severity, exploitation and fixes.
Nltk 14Picklescan 6Langflow 5Omnigent 4Nautobot 4Urllib3 4Litellm 3Cryptography 3Pypdf 3Vllm 3Salt 3Oauthlib 2OctoPrint 2Apache-airflow 2Flyto-core 2Sglang 2Lmdeploy 2Django-allauth 2Pydantic-ai-slim 2Mlflow 2Praisonaiagents 2Pydantic-ai 2Docling 1Lmcache 1Tensorzero 1Tinytag 1Shiny 1Pacioli-guard 1Social-auth-core 1Netlicensing-mcp 1Nicegui 1Taguette 1Mad-proxy 1Pyminizip 1Paramiko 1M2crypto 1Claude-agent-sdk 1Pyspark 1Starlette 1Pip 1
CVE-2021-3572
Medium · 5.7
CWE-20 Nov 10, 2021
Improper Input Validation in pip
A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.
CVE-2021-28363
Medium · 6.5
CWE-295 Mar 15, 2021
Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection
The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to HTTPS proxies. The initial connection to the HTTPS proxy (if an SSLContext isn't given via proxy_config) doesn't verify the hostname of the certificate. This means certificates for different servers that still validate properly with the default urllib3 SSLContext will be silently accepted.
CVE-2020-13927
Critical · 9.8
KEV Urgent · 83 Public exploit CWE-306 Nov 10, 2020
Apache Airflow's Experimental API Authentication Bypass
The previous default setting for Airflow's Experimental API was to allow all API requests without authentication, but this poses security risks to users who miss this fact. From Airflow 1.10.11 the default has been changed to deny all requests by default and is documented at https://airflow.apache.org/docs/1.10.11/security.html#api-authentication. Note this change fixes it for new installs but existing users need to change their config to default `[api]auth_backend = airflow.api.auth.backend.deny_all` as mentioned in the Updating Guide: https://github.com/apache/airflow/blob/1.10.11/UPDATING.md#experimental-api-will-deny-all-request-by-default
CVE-2020-16846
Critical · 9.8
KEV Urgent · 83 Public exploit CWE-78 Nov 6, 2020
SaltStack Salt Shell Injection Vulnerability
An issue was discovered in SaltStack Salt through 3002. Sending crafted web requests to the Salt API, with the SSH client enabled, can result in shell injection.
CVE-2020-11978
High · 8.8
KEV Urgent · 76 Public exploit CWE-78 Jul 16, 2020
Apache Airflow Command Injection
An issue was found in Apache Airflow versions 1.10.10 and below. A remote code/command injection vulnerability was discovered in one of the example DAGs shipped with Airflow which would allow any authenticated user to run arbitrary commands as the user running airflow worker/scheduler (depending on the executor in use). If you already have examples disabled by setting load_examples=False in the config then you are not vulnerable.
CVE-2020-11651
Critical · 9.8
KEV Urgent · 83 Public exploit Apr 30, 2020
SaltStack Salt Authentication Bypass Vulnerability
An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class does not properly validate method calls. This allows a remote user to access some methods without authentication. These methods can be used to retrieve user tokens from the salt master and/or run arbitrary commands on salt minions.
CVE-2020-11652
Medium · 6.5
KEV Urgent · 73 Public exploit CWE-22 Apr 30, 2020
SaltStack Salt Path Traversal Vulnerability
An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class allows access to some methods that improperly sanitize paths. These methods allow arbitrary directory access to authenticated users.
CVE-2019-11340
Medium · 5.9
CWE-20 Apr 19, 2019
Matrix Sydent mishandles emails
util/emailutils.py in Matrix Sydent before 1.0.2 mishandles registration restrictions that are based on e-mail domain, if the allowed_local_3pids option is enabled. This occurs because of potentially unwanted behavior in Python, in which an email.utils.parseaddr call on user@bad.example.net@good.example.com returns the user@bad.example.net substring.