CVE-2000-0292
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 · uneditedThe Adtran MX2800 M13 Multiplexer allows remote attackers to cause a denial of service via a ping flood to the Ethernet interface, which causes the device to crash.
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 · moderate confidenceThe Adtran MX2800 M13 Multiplexer suffers from a denial-of-service vulnerability where a ping flood (ICMP flood) directed at the Ethernet interface causes the device to crash. The device lacks proper rate limiting or input validation to handle excessive ICMP traffic, leading to a complete service interruption.
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= m13CVSS 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 the device modelLog into the device CLI or check hardware labeling to confirm the exact model is Adtran MX2800 M13 MultiplexerAffected if The device is an Adtran MX2800 M13 multiplexer running firmware version m13
-
Check the firmware versionUse the device's command-line interface (typically via console or telnet/ssh) and run the command to display firmware version, such as 'show version' or 'show system'Affected if The firmware version displayed is 'm13' or falls within the affected version range
-
Verify ICMP echo response is enabledCheck the device configuration for ICMP echo settings using commands like 'show ip interface' or 'show icmp' to see if ping responses are permitted on the Ethernet interfaceAffected if ICMP echo responses are enabled and allowed on the Ethernet interface with no filtering configured
-
Confirm no ICMP rate limiting is configuredExamine the device's access control or traffic management configuration using commands like 'show access-list' or 'show rate-limit' to see if any ICMP rate limiting or traffic policing is appliedAffected if No ICMP-specific rate limiting, traffic shaping, or access list filtering is configured for inbound ICMP traffic
-
Test ICMP traffic handling (optional passive check)Observe network traffic to the device using a network analyzer or monitoring tool to verify how the device processes ICMP packets; do not actively ping flood as that would cause the very DoS you are testing forAffected if The device processes all incoming ICMP packets without throttling or drop policies
You are affected if you have an Adtran MX2800 M13 multiplexer with firmware version m13 where ICMP echo responses are enabled and no rate limiting or filtering is configured for ICMP traffic.
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 dataImplement network-level filtering (firewall or upstream network device) to rate-limit or block unsolicited ICMP traffic directed at the multiplexer. If the device firmware supports it, disable ICMP echo responses on the Ethernet interface.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0292 — 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-2000-0292 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