# CVE-1999-0060: Denial of service in n/a

> Attackers can cause a denial of service on Ascend MAX and Pipeline routers by sending a malformed packet to the discard port.

- **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:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-5j44-w6q9-hxx4

## What is CVE-1999-0060?

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

### Official description

Attackers can cause a denial of service in Ascend MAX and Pipeline routers with a malformed packet to the discard port, which is used by the Java Configurator tool.

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

It affects 3 products.


Products: Lucent Ascend Max Router, Lucent Ascend Pipeline Router, Lucent Ascend Tnt Router.

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

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

## Is CVE-1999-0060 being exploited?

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

Public exploit code:

- Lucent Ascend MAX 5.0/Pipeline 6.0/TNT 1.0/2.0 Router - MAX UDP Port 9 (1) (exploitdb)
- Lucent Ascend MAX 5.0/Pipeline 6.0/TNT 1.0/2.0 Router - MAX UDP Port 9 (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-2148](https://insights.sbomify.com/CVE-2002-2148/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0060 is a medium-severity denial of service vulnerability in n/a, published on 29 Sep 1999. 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-1999-0060 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-1999-0060/ (Markdown: https://insights.sbomify.com/CVE-1999-0060/index.md)
```

## Sources

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

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