# CVE-2002-1644: Privilege escalation in n/a

> Attackers can gain privileges in SSH Secure Shell when running without a PTY due to missing process group isolation.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jg6f-f7v8-2wh4

## What is CVE-2002-1644?

CVE-2002-1644 is a high-severity vulnerability in n/a, published on 28 Mar 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SSH Secure Shell for Servers and SSH Secure Shell for Workstations 2.0.13 through 3.2.1, when running without a PTY, does not call setsid to remove the child process from the process group of the parent process, which allows attackers to gain certain privileges.

## Which versions are affected by CVE-2002-1644?

It affects 1 product.


Products: Ssh Ssh2.

## How do I fix CVE-2002-1644?

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

## Is CVE-2002-1644 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1645](https://insights.sbomify.com/CVE-2002-1645/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-1029](https://insights.sbomify.com/CVE-1999-1029/): Information disclosure in n/a (high 7.5)
- [CVE-2001-0364](https://insights.sbomify.com/CVE-2001-0364/): Denial of service in n/a (medium 5.0)
- [CVE-1999-1231](https://insights.sbomify.com/CVE-1999-1231/): Information disclosure in n/a (medium 5.0)
- [CVE-1999-1159](https://insights.sbomify.com/CVE-1999-1159/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1644 and fix it if it is affected.

What it is: CVE-2002-1644 is a high-severity vulnerability in n/a, published on 28 Mar 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1644 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-2002-1644/ (Markdown: https://insights.sbomify.com/CVE-2002-1644/index.md)
```

## Sources

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

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