# CVE-2017-12852: Numpy missing input validation

> Attackers can cause a denial of service by passing empty lists or arrays to the numpy.pad function, triggering an infinite loop.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-frgw-fgh6-9g52, PYSEC-2017-1, SUSE-RU-2017:3010-1, SUSE-SU-2022:3954-1, UBUNTU-CVE-2017-12852

## What is CVE-2017-12852?

CVE-2017-12852 is a high-severity denial of service vulnerability in n/a, published on 15 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The numpy.pad function in Numpy 1.13.1 and older versions is missing input validation. An empty list or ndarray will stick into an infinite loop, which can allow attackers to cause a DoS attack.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2017-12852?

3 open source packages ship an affected version, including numpy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `numpy` | PyPI | All versions | 1.13.3 |
| `numpy` | PyPI | All versions | 1.13.3 |
| `numpy` | PyPI | All versions | 1.13.3 |
| `python-numpy_1_13_3-gnu-hpc` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 1.13.3-4.6.1 |
| `python-numpy` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.8.0-5.19.1 |
| `python-numpy` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.8.0-5.19.1 |
| `python-numpy` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.8.0-5.19.1 |

Products: Numpy Numpy.

## How do I fix CVE-2017-12852?

Upgrade numpy to 1.13.3 or later.

## Is CVE-2017-12852 being exploited?

There is no known exploitation of CVE-2017-12852 in the wild and no public exploit code.

Public exploit code:

- test the CVE-2017-12852 in numpy v1.13.1 and v1.13.3 has fixed the bug  (github_poc): https://github.com/BT123/numpy-1.13.1

## Other vulnerabilities in n/a

- [CVE-2021-41496](https://insights.sbomify.com/CVE-2021-41496/): Buffer Copy without Checking Size of Input in NumPy (medium 5.5)
- [CVE-2014-1858](https://insights.sbomify.com/CVE-2014-1858/): Arbitrary file write in NumPy (medium 5.5)
- [CVE-2021-33430](https://insights.sbomify.com/CVE-2021-33430/): NumPy Buffer Overflow (Disputed) (medium 5.3)
- [CVE-2021-34141](https://insights.sbomify.com/CVE-2021-34141/): Incorrect Comparison in NumPy (medium 5.3)
- [CVE-2021-41495](https://insights.sbomify.com/CVE-2021-41495/): NumPy NULL Pointer Dereference (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12852 and fix it if it is affected.

What it is: CVE-2017-12852 is a high-severity denial of service vulnerability in n/a, published on 15 Aug 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-2017-12852 in the wild and no public exploit code.

Affected packages and fixed versions:
- numpy (PyPI): affected all versions; fixed in 1.13.3
- numpy (PyPI): affected all versions; fixed in 1.13.3
- numpy (PyPI): affected all versions; fixed in 1.13.3

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-2017-12852/ (Markdown: https://insights.sbomify.com/CVE-2017-12852/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-12852
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-12852
- OSV: https://osv.dev/vulnerability/CVE-2017-12852

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-12852/
Summaries are generated and may contain mistakes; the official description above is the record.