# CVE-2003-0787: Memory corruption in n/a

> Attackers can exploit a memory corruption flaw in OpenSSH's PAM conversation function to modify the stack and potentially gain elevated privileges.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0787, GHSA-jmj3-c2mm-6fgh

## What is CVE-2003-0787?

CVE-2003-0787 is a high-severity memory corruption vulnerability in OpenSSH, published on 25 Sep 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PAM conversation function in OpenSSH 3.7.1 and 3.7.1p1 interprets an array of structures as an array of pointers, which allows attackers to modify the stack and possibly gain privileges.

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

It affects 1 product.


Products: OpenSSH.

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

Upgrade to a fixed version.

## Is CVE-2003-0787 being exploited?

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

## Other vulnerabilities in OpenSSH

- [CVE-2003-0786](https://insights.sbomify.com/CVE-2003-0786/): Auth bypass in n/a (critical 10.0)
- [CVE-2003-0693](https://insights.sbomify.com/CVE-2003-0693/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0640](https://insights.sbomify.com/CVE-2002-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0144](https://insights.sbomify.com/CVE-2001-0144/): Integer overflow in n/a (critical 10.0)
- [CVE-2000-0999](https://insights.sbomify.com/CVE-2000-0999/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0787 is a high-severity memory corruption vulnerability in OpenSSH, published on 25 Sep 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0787 in the wild and no public exploit code.

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

## Sources

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

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