# CVE-2016-8859: Integer overflow in n/a

> Integer overflows in the TRE library allow attackers to trigger out-of-bounds writes via crafted regex patterns, potentially leading to code execution or crashes.

- **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:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2016-8859, DEBIAN-CVE-2016-8859, DLA-687-1, GHSA-2r68-mjqv-c389, UBUNTU-CVE-2016-8859, openSUSE-SU-2024:11475-1

## What is CVE-2016-8859?

CVE-2016-8859 is a critical vulnerability in n/a, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple integer overflows in the TRE library and musl libc allow attackers to cause memory corruption via a large number of (1) states or (2) tags, which triggers an out-of-bounds write.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-8859?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `agrep` | openSUSE:Tumbleweed | All versions | 0.8.0_git201402282055-5.8 |

Products: Etalabs Musl.

## How do I fix CVE-2016-8859?

Apply the vendor's patch.

## Is CVE-2016-8859 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2114](https://insights.sbomify.com/CVE-2012-2114/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8859 and fix it if it is affected.

What it is: CVE-2016-8859 is a critical vulnerability in n/a, published on 13 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-2016-8859 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-2016-8859/ (Markdown: https://insights.sbomify.com/CVE-2016-8859/index.md)
```

## Sources

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

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