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

> Local attackers can exploit an integer overflow in the kernel to execute arbitrary code with elevated privileges.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 7 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pqrq-q9c7-wrj4

## What is CVE-2016-6241?

CVE-2016-6241 is a high-severity vulnerability in Openbsd Openbsd, published on 7 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in the amap_alloc1 function in OpenBSD 5.8 and 5.9 allows local users to execute arbitrary code with kernel privileges via a large size value.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Openbsd Openbsd.

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

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

## Is CVE-2016-6241 being exploited?

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

## Other vulnerabilities in Openbsd Openbsd

- [CVE-2007-1365](https://insights.sbomify.com/CVE-2007-1365/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0220](https://insights.sbomify.com/CVE-2004-0220/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0083](https://insights.sbomify.com/CVE-2004-0083/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0084](https://insights.sbomify.com/CVE-2004-0084/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0284](https://insights.sbomify.com/CVE-2001-0284/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6241 is a high-severity vulnerability in Openbsd Openbsd, published on 7 Mar 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-2016-6241 in the wild and no public exploit code.

Affected product: Openbsd Openbsd. 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-6241/ (Markdown: https://insights.sbomify.com/CVE-2016-6241/index.md)
```

## Sources

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

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