Skip to content
Sign in
CVE-2022-216688.0HighCWE-78

CVE-2022-21668: Pipenv's requirements.txt parsing allows malicious index url in comments

pypa · pipenv

Vendor fix available · Affected: pypa pipenv · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

3.9%probability of exploitation in the next 30 days
90th percentile
050100

Higher than 90% of scored CVEs

8.0HighCVSS 3.1
LowHigh

DescriptionCVE.org

pipenv is a Python development workflow tool. Starting with version 2018.10.9 and prior to version 2022.1.8, a flaw in pipenv's parsing of requirements files allows an attacker to insert a specially crafted string inside a comment anywhere within a requirements.txt file, which will cause victims who use pipenv to install the requirements file to download dependencies from a package index server controlled by the attacker. By embedding malicious code in packages served from their malicious index server, the attacker can trigger arbitrary remote code execution (RCE) on the victims' systems. If an attacker is able to hide a malicious `--index-url` option in a requirements file that a victim installs with pipenv, the attacker can embed arbitrary malicious code in packages served from their malicious index server that will be executed on the victim's host during installation (remote code execution/RCE). When pip installs from a source distribution, any code in the setup.py is executed by the install process. This issue is patched in version 2022.1.8. The GitHub Security Advisory contains more information about this vulnerability.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • pypa · pipenv>= 2018.10.9, < 2022.1.8

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
pypa
Published
January 2022

CoverageNo articles yet

No CyberSIXT article names CVE-2022-21668 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in