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

> Attackers can cause a denial of service via a negative length value in the memset function of the uClibc library.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 27 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-6264, GHSA-5f7g-9m8m-qhpv

## What is CVE-2016-6264?

CVE-2016-6264 is a high-severity vulnerability in n/a, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer signedness error in libc/string/arm/memset.S in uClibc and uClibc-ng before 1.0.16 allows context-dependent attackers to cause a denial of service (crash) via a negative length value to the memset function.

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

It affects 2 products.


Products: Uclibc-Ng Project Uclibc-Ng, Uclibc Uclibc.

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

Upgrade to a fixed version.

## Is CVE-2016-6264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43523](https://insights.sbomify.com/CVE-2021-43523/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2016-2224](https://insights.sbomify.com/CVE-2016-2224/): Denial of service in n/a (high 7.5)
- [CVE-2016-2225](https://insights.sbomify.com/CVE-2016-2225/): Denial of service in n/a (high 7.5)
- [CVE-2021-27419](https://insights.sbomify.com/CVE-2021-27419/): uClibc-ng Integer Overflow or Wraparound (high 7.3)
- [CVE-2022-30295](https://insights.sbomify.com/CVE-2022-30295/): Other in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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