PYSEC-2022-6

Vulnerability from pysec - Published: 2022-01-10 21:15 - Updated: 2022-01-19 19:22
VLAI?
Details

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.

Impacted products
Name purl
pipenv pkg:pypi/pipenv

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "pipenv",
        "purl": "pkg:pypi/pipenv"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "439782a8ae36c4762c88e43d5f0d8e563371b46f"
            }
          ],
          "repo": "https://github.com/pypa/pipenv",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "2018.10.9"
            },
            {
              "fixed": "2022.1.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2018.10.13",
        "2018.10.9",
        "2018.11.14",
        "2018.11.26",
        "2020.11.15",
        "2020.11.4",
        "2020.4.1b1",
        "2020.4.1b2",
        "2020.5.28",
        "2020.6.2",
        "2020.8.13",
        "2021.11.15",
        "2021.11.23",
        "2021.11.5",
        "2021.11.5.post0",
        "2021.11.9",
        "2021.5.29"
      ]
    }
  ],
  "aliases": [
    "CVE-2022-21668",
    "GHSA-qc9x-gjcv-465w"
  ],
  "details": "pipenv is a Python development workflow tool. Starting with version 2018.10.9 and prior to version 2022.1.8, a flaw in pipenv\u0027s 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\u0027 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\u0027s 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.",
  "id": "PYSEC-2022-6",
  "modified": "2022-01-19T19:22:23.694218Z",
  "published": "2022-01-10T21:15:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/pypa/pipenv/releases/tag/v2022.1.8"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/pypa/pipenv/security/advisories/GHSA-qc9x-gjcv-465w"
    },
    {
      "type": "FIX",
      "url": "https://github.com/pypa/pipenv/commit/439782a8ae36c4762c88e43d5f0d8e563371b46f"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…