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

> Local attackers can gain privileges because the sendfiled utility fails to drop privileges when sending notification emails.

- **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:** 27 Jul 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7pw9-r7h7-2x88

## What is CVE-2001-0623?

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

### Official description

sendfiled, as included with Simple Asynchronous File Transfer (SAFT), on various Linux systems does not properly drop privileges when sending notification emails, which allows local attackers to gain privileges.

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

It affects 1 product.


Products: Sendfile Sendfile.

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

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

## Is CVE-2001-0623 being exploited?

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

Public exploit code:

- Sendfile 1.x/2.1 - Local Privileged Arbitrary Command Execution (exploitdb)
- Sendfile 1.x/2.1 - Forced Privilege Lowering Failure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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