Vulnerability Database · PyPI · pycrypto · Version
pycrypto 2.3.0
2.3.0 is affected by 8 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 2 Medium 1 Low 0 Unrated 4
-
Released 17 Dec 2010
Licence non-standard
Also known from other sources 8
Newer releases 9
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
pycrypto 2.3.0 vulnerabilities
8 vulnerabilities cover pycrypto 2.3.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2013-7459: Buffer Overflow in pycrypto | 9.8 critical | No fix published | 14 Dec 2018 |
| CVE-2013-1445: PyCrypto PRNG Reseeding Vulnerability | 7.5 high | 2.6.1 | 17 May 2022 |
| CVE-2018-6594: Weak ElGamal Key Parameters in PyCrypto | 7.5 high | No fix published | 12 Jul 2018 |
| CVE-2012-2417: PyCrypto makes Use of Insufficiently Random Values | 5.3 medium | 2.6 | 17 May 2022 |
| CVE-2018-6594: Weak ElGamal Key Parameters in PyCrypto | N/A unrated | No fix published | 03 Feb 2018 |
| CVE-2013-7459: Heap-based buffer overflow in Python Cryptography Toolkit (pycrypto) | N/A unrated | 8dbe0dc3eea5c689d4f76b37b93fe216cf1f00d4 | 15 Feb 2017 |
| CVE-2013-1445: Vulnerability in PyCrypto allows sensitive information leakage | N/A unrated | 19dcf7b15d61b7dc1a125a367151de40df6ef175 | 26 Oct 2013 |
| CVE-2012-2417: PyCrypto ElGamal Key Generation Vulnerability | N/A unrated | 9f912f13df99ad3421eff360d6a62d7dbec755c2 | 17 Jun 2012 |
Looking for another version, or everything Vulert holds for pycrypto?
Questions
About pycrypto 2.3.0
Is pycrypto 2.3.0 vulnerable?
Yes. 8 vulnerabilities in the Vulert database cover pycrypto 2.3.0: 1 critical, 2 high, 1 medium and 0 low, plus 4 not yet rated. Each entry above names the fixed version to move to.
Is 2.3.0 the latest release of pycrypto?
No. 2.3.0 was published 17 Dec 2010, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor pycrypto for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pycrypto version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.