# CVE-2013-7459: Buffer Overflow in pycrypto > Remote attackers can execute arbitrary code via a heap-based buffer overflow in the Python Cryptography Toolkit's ALGnew function. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Feb 2017 - **Updated:** 6 Aug 2024 - **Also known as:** DLA-773-1, GHSA-cq27-v7xp-c356, MGASA-2017-0032, PYSEC-2017-94, SUSE-SU-2017:1744-1, SUSE-SU-2017:2350-1, UBUNTU-CVE-2013-7459, USN-3199-1, USN-3199-2 ## What is CVE-2013-7459? CVE-2013-7459 is a critical memory corruption vulnerability in Fedoraproject Fedora, published on 15 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Heap-based buffer overflow in the ALGnew function in block_templace.c in Python Cryptography Toolkit (aka pycrypto) allows remote attackers to execute arbitrary code as demonstrated by a crafted iv parameter to cryptmsg.py. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2013-7459? 3 open source packages ship an affected version, including pycrypto. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pycrypto` | PyPI | All versions | None | | `pycrypto` | PyPI | All versions to 2.6.1 | None | | `pycrypto` | PyPI | All versions to 2.6.1 | None | | `python-paramiko` | SUSE:Enterprise Storage 3 | All versions | 1.15.2-2.3.1 | | `python-pycrypto` | SUSE:Enterprise Storage 3 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Enterprise Storage 4 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Linux Enterprise Module for Advanced Systems Management 12 | All versions | 2.6.1-10.3.1 | | `python-paramiko` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 1.15.2-2.6.1 | | `python-pycrypto` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Linux Enterprise Module for Web and Scripting 12 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Linux Enterprise Point of Sale 12 SP2 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLS | All versions | 2.6.1-5.1 | | `python-pycrypto` | SUSE:Linux Enterprise Server 11 SP4-CLIENT-TOOLS | All versions | 2.6.1-5.1 | | `python-pycrypto` | SUSE:Manager Client Tools 12 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Manager Proxy 3.0 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Manager Proxy 3.1 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Manager Server 3.0 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:Manager Server 3.1 | All versions | 2.6.1-10.3.1 | | `python-paramiko` | SUSE:OpenStack Cloud 6 | All versions | 1.15.2-2.3.1 | | `python-pycrypto` | SUSE:OpenStack Cloud 6 | All versions | 2.6.1-10.3.1 | | `python-pycrypto` | SUSE:OpenStack Cloud 7 | All versions | 2.6.1-10.3.1 | Products: Dlitz Pycrypto, Fedoraproject Fedora. ## How do I fix CVE-2013-7459? Upgrade to a fixed version. ## Is CVE-2013-7459 being exploited? There is no known exploitation of CVE-2013-7459 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2013-1445](https://insights.sbomify.com/CVE-2013-1445/): PyCrypto does not properly reseed PRNG before allowing access (medium 4.3) - [CVE-2012-2417](https://insights.sbomify.com/CVE-2012-2417/): PyCrypto makes Use of Insufficiently Random Values (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-7459 and fix it if it is affected. What it is: CVE-2013-7459 is a critical memory corruption vulnerability in Fedoraproject Fedora, published on 15 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-7459 in the wild and no public exploit code. Affected packages and fixed versions: - pycrypto (PyPI): affected all versions; no fix listed - pycrypto (PyPI): affected all versions up to 2.6.1; no fix listed - pycrypto (PyPI): affected all versions up to 2.6.1; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2013-7459/ (Markdown: https://insights.sbomify.com/CVE-2013-7459/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-7459 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-7459 - OSV: https://osv.dev/vulnerability/CVE-2013-7459 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-7459/ Summaries are generated and may contain mistakes; the official description above is the record.