CVE-1999-0060
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAttackers 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA denial-of-service vulnerability exists in Ascend MAX and Pipeline routers where sending a malformed packet to the discard port (used by the Java Configurator tool) causes the device to crash or become unresponsive.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0= 2.0= 3.0= 4.0= 5.0= 1.0= 2.0= 3.0= 4.0= 5.0= 6.0= 1.0= 2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Ascend router models on the networkInventory network devices and check for Lucent Ascend MAX, Pipeline, or Tnt routers by querying SNMP, checking device banners, or reviewing network topology documentationAffected if Any of these three router models (MAX, Pipeline, or Tnt) are present in the environment
-
Confirm firmware versionAccess the router console or management interface and run the version command to display the installed firmware versionAffected if The firmware version matches 1.0, 2.0, 3.0, 4.0, or 5.0 for MAX; 1.0-6.0 for Pipeline; or 1.0 or 2.0 for Tnt
-
Check if discard port is listeningPerform a port scan or use 'netstat' from an adjacent system to check if UDP port 9 (discard port) is open and listening on the routerAffected if UDP port 9 is open and accessible on the device
-
Verify Java Configurator is enabledCheck the router configuration for Java Configurator service settings, typically accessible via the management interface or configuration filesAffected if Java Configurator is enabled and the discard port is in use
A user is affected if they have a Lucent Ascend MAX, Pipeline, or Tnt router running the specified firmware versions with the discard port open and Java Configurator enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince these are legacy 1999-era routers likely past end-of-life, apply network access controls to block external traffic to the discard port, or replace with current hardware if the devices are still in production use.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-1999-0060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data