CVE-1999-1201
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 · uneditedWindows 95 and Windows 98 systems, when configured with multiple TCP/IP stacks bound to the same MAC address, allow remote attackers to cause a denial of service (traffic amplification) via a certain ICMP echo (ping) packet, which causes all stacks to send a ping response, aka TCP Chorusing.
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 confidenceWindows 95 and Windows 98 systems configured with multiple TCP/IP stacks bound to the same MAC address will cause all stacks to respond to a single ICMP echo request, resulting in traffic amplification and potential denial of service.
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 versionsall 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 Windows versionOpen Command Prompt and run 'winver' or check System Properties (right-click My Computer, select Properties). Look for Windows 95 or Windows 98 in the OS name.Affected if The system is running any version of Microsoft Windows 95 or Microsoft Windows 98.
-
Open Network Connections control panelOpen Control Panel, then double-click Network (or run 'ncpa.cpl' from Run dialog). This displays all installed network protocols and bindings.Affected if The network configuration panel is accessible and shows network adapters.
-
Examine TCP/IP protocol bindingsFor each network adapter listed, right-click and select Properties. Look for 'TCP/IP ->' entries in the list of installed components. Count how many TCP/IP protocol entries are bound to the same adapter.Affected if More than one TCP/IP protocol entry is bound to a single network adapter (same MAC address).
-
Identify duplicate MAC address bindingsIn Network Connections, select each adapter and view its Configuration. Check the adapter's properties for the MAC address (also called Physical Address or Node Address). Compare MAC addresses across multiple TCP/IP stack entries.Affected if Two or more TCP/IP stacks are bound to network adapters sharing the same MAC address.
The environment is affected if running Windows 95 or Windows 98 AND has multiple TCP/IP protocol stacks bound to network adapters with identical MAC addresses.
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 dataRemove duplicate TCP/IP stack bindings to the same MAC address, or migrate away from Windows 95/98 to a supported operating system.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1201 — 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-1201 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