# CVE-2003-0740: Information disclosure in n/a

> Local attackers can hijack the Stunnel server by exploiting a leaked privileged file descriptor, leading to potential privilege escalation.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0740, GHSA-94h5-4g3p-4v6g

## What is CVE-2003-0740?

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

### Official description

Stunnel 4.00, and 3.24 and earlier, leaks a privileged file descriptor returned by listen(), which allows local users to hijack the Stunnel server.

## Which versions are affected by CVE-2003-0740?

It affects 1 product.


Products: Stunnel Stunnel.

## How do I fix CVE-2003-0740?

Upgrade to a fixed version.

## Is CVE-2003-0740 being exploited?

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

Public exploit code:

- Stunnel 3.24/4.00 - Daemon Hijacking (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0060](https://insights.sbomify.com/CVE-2001-0060/): Other in n/a (critical 10.0)
- [CVE-2011-2940](https://insights.sbomify.com/CVE-2011-2940/): Memory corruption in n/a (critical 9.3)
- [CVE-2021-20230](https://insights.sbomify.com/CVE-2021-20230/): Auth bypass in stunnel (high 7.5)
- [CVE-2008-2400](https://insights.sbomify.com/CVE-2008-2400/): Unspecified vulnerability in stunnel before 4.23, when running as a service on Windows, allows local users to gain privileges via unknown attack vectors. (high 7.2)
- [CVE-2008-2420](https://insights.sbomify.com/CVE-2008-2420/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0740 and fix it if it is affected.

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

## Sources

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

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