# CVE-2002-1322: Denial of service in n/a

> Remote attackers can crash the Rational ClearCase server by sending malicious packets to port 371, causing a denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 27 Nov 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gp49-xhgq-399v

## What is CVE-2002-1322?

CVE-2002-1322 is a medium-severity denial of service vulnerability in n/a, published on 27 Nov 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rational ClearCase 4.1, 2002.05, and possibly other versions allows remote attackers to cause a denial of service (crash) via certain packets to port 371, e.g. via nmap.

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

It affects 1 product.


Products: Rational Software Clearcase.

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

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

## Is CVE-2002-1322 being exploited?

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

Public exploit code:

- Rational ClearCase 4.1 - Portscan Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0855](https://insights.sbomify.com/CVE-2001-0855/): Memory corruption in n/a (high 7.2)
- [CVE-1999-0350](https://insights.sbomify.com/CVE-1999-0350/): Race condition in n/a (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1322 is a medium-severity denial of service vulnerability in n/a, published on 27 Nov 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1322 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-2002-1322/ (Markdown: https://insights.sbomify.com/CVE-2002-1322/index.md)
```

## Sources

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

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