CVE-2000-0451
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 Intel express 8100 ISDN router allows remote attackers to cause a denial of service via oversized or fragmented ICMP packets.
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 · low confidenceThe Intel Express 8100 ISDN router contains a vulnerability where oversized or fragmented ICMP packets can cause the device to crash or become unresponsive, resulting in a denial of service. This likely indicates insufficient bounds checking or error handling in the router's ICMP packet processing logic.
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 dataall versionsCVSS 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.
-
Confirm the device model in your network inventoryReview asset management records, network topology documentation, or physically inspect devices to identify any Intel Express 8100 ISDN routers currently deployed in your environmentAffected if An Intel Express 8100 ISDN router is present in the network
-
Verify network accessibility of the deviceAttempt to ping the IP address assigned to the Intel Express 8100 router using the ping command from an internal network host. Also check if the device is reachable via SNMP if configuredAffected if The device responds to ICMP echo requests, indicating it is accessible on the network
-
Check router status and uptimeAccess the router administration interface or check SNMP metrics for uptime and responsiveness. Look for frequent resets or unexplained downtime in logsAffected if The device shows intermittent unresponsiveness, crashes, or requires frequent reboots
-
Identify ICMP exposure at network perimeterReview firewall or edge router configurations to determine whether oversized or fragmented ICMP packets are permitted through to internal network segments where the router residesAffected if Fragmented ICMP packets are allowed to reach the device without filtering
If an Intel Express 8100 ISDN router is deployed and reachable on your network, you are affected since all versions of this device are vulnerable to denial of service from oversized or fragmented ICMP packets.
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 dataNetwork perimeter devices should be configured to filter or block oversized and fragmented ICMP packets destined for the router. If the device is still in production use, strongly consider replacement with currently-supported hardware, as Intel Express 8100 ISDN routers are obsolete and likely no longer receive firmware updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0451 — 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-0451 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