CVE-2013-1633 json
Setuptools vulnerable to Man-in-the-middle attacks
published 13y ago modified 4mo ago also GHSA-27x4-j476-jp5f , PYSEC-2013-22 , EUVD-2013-0040
- cvss
- 8.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
easy_install in setuptools before 0.7 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execute arbitrary code via a crafted response to the default use of the product.
Patch / fix
- pypi setuptools 0.7
Is CVE-2013-1633 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-1633 updated cvss 4.4
python-setuptools: easy_install insecure installation mechanism
-
Red Hat OpenShift Enterprise 1 python-virtualenvaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 5 python-setuptools Red Hat Enterprise Linux 6 python-setuptoolsaffected: no fix available
-
Red Hat Enterprise MRG 1 python-setuptoolsaffected: no fix planned “Will not fix”
-
Red Hat Software Collections python27-python-setuptools, python27-python-virtualenv, python33-python-setuptools, python33-python-virtualenvaffected: no fix available
-
Red Hat Enterprise Linux 7 python-setuptools, python-virtualenvnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.96% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | setuptools | <0.7 |
0.7 |
Classification
References
-
pypi.python.org
/pypi/setuptools/0.9.8#changes
web, vendor-advisory
-
reddit.com
/r/Python/comments/17rfh7/warning_dont_use_pip_in_an_untrusted_network_a/
web
-
nvd.nist.gov
/vuln/detail/CVE-2013-1633
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/setuptools/PYSEC-2013-22.yaml
web
-
github.com
/pypa/setuptools
package
-
reddit.com
/r/Python/comments/17rfh7/warning_dont_use_pip_in_an_untrusted_network_a
web
-
github.com
/advisories/GHSA-27x4-j476-jp5f
advisory
Sources
- CVE List CVE-2013-1633
- GitHub Advisory GHSA-27x4-j476-jp5f
- NVD CVE-2013-1633
- OSV PYSEC-2013-22
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.