# CVE-2001-1327: Privilege escalation in n/a

> Local users can gain root privileges by exploiting vulnerabilities in the setuid root pmake utility on Turbolinux systems.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vw25-v3xr-366m

## What is CVE-2001-1327?

CVE-2001-1327 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

pmake before 2.1.35 in Turbolinux 6.05 and earlier is installed with setuid root privileges, which could allow local users to gain privileges by exploiting vulnerabilities in pmake or programs that are used by pmake.

## Which versions are affected by CVE-2001-1327?

It affects 1 product.


Products: Berkeley Softworks Pmake.

## How do I fix CVE-2001-1327?

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

## Is CVE-2001-1327 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1327 and fix it if it is affected.

What it is: CVE-2001-1327 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. 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-2001-1327 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-2001-1327/ (Markdown: https://insights.sbomify.com/CVE-2001-1327/index.md)
```

## Sources

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

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