# CVE-1999-1321: Memory corruption in n/a

> Remote attackers can execute arbitrary commands or cause denial of service via a buffer overflow in the SSH client when Kerberos is enabled.

- **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:** No
- **Published:** 9 Mar 2002
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-4vqr-h3fp-wv83

## What is CVE-1999-1321?

CVE-1999-1321 is a high-severity memory corruption vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in ssh 1.2.26 client with Kerberos V enabled could allow remote attackers to cause a denial of service or execute arbitrary commands via a long DNS hostname that is not properly handled during TGT ticket passing.

## Which versions are affected by CVE-1999-1321?

It affects 1 product.


Products: Mit Kerberos.

## How do I fix CVE-1999-1321?

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

## Is CVE-1999-1321 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4212](https://insights.sbomify.com/CVE-2009-4212/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0523](https://insights.sbomify.com/CVE-2004-0523/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0283](https://insights.sbomify.com/CVE-2010-0283/): Denial of service in n/a (high 7.8)
- [CVE-2018-5709](https://insights.sbomify.com/CVE-2018-5709/): Integer overflow in n/a (high 7.5)
- [CVE-2003-0138](https://insights.sbomify.com/CVE-2003-0138/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1321 and fix it if it is affected.

What it is: CVE-1999-1321 is a high-severity memory corruption vulnerability in n/a, published on 9 Mar 2002. 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-1999-1321 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-1999-1321/ (Markdown: https://insights.sbomify.com/CVE-1999-1321/index.md)
```

## Sources

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

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