# CVE-2007-1189: Integer overflow in n/a

> Local attackers can exploit an integer overflow in the Plan 9 kernel to overwrite memory and gain elevated privileges or execute code.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 2 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4763-4594-fp9p

## What is CVE-2007-1189?

CVE-2007-1189 is a high-severity vulnerability in n/a, published on 2 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in the envwrite function in the Alcatel-Lucent Bell Labs Plan 9 kernel allows local users to overwrite certain memory addresses with kernel memory via a large n argument, as demonstrated by (1) modifying the iseve function to gain privileges and (2) making the devpermcheck function grant unrestricted device permissions.

## Which versions are affected by CVE-2007-1189?

It affects 1 product.


Products: Bell Labs Plan 9.

## How do I fix CVE-2007-1189?

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

## Is CVE-2007-1189 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1189 exists.

Public exploit code:

- Plan 9 Kernel - 'devenv.c OTRUNC/pwrite' Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1189 and fix it if it is affected.

What it is: CVE-2007-1189 is a high-severity vulnerability in n/a, published on 2 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1189 exists.

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

## Sources

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

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