# CVE-2017-13666: Integer overflow in n/a

> An integer underflow in x265 allows attackers to cause a denial of service via a small height value.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rvv7-6w95-x7c7, UBUNTU-CVE-2017-13666

## What is CVE-2017-13666?

CVE-2017-13666 is a medium-severity vulnerability in n/a, published on 24 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An integer underflow vulnerability exists in pixel-a.asm, the x86 assembly code for planeClipAndMax() in MulticoreWare x265 through 2.5, as used in libbpg and other products. A small height value can cause an integer underflow, which leads to a crash. This is a different vulnerability than CVE-2017-8906.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

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

It affects 1 product.


Products: Multicorewareinc X265.

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

No fix has been published for CVE-2017-13666 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-13666 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-13666 is a medium-severity vulnerability in n/a, published on 24 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-13666 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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