CVE-1999-0875
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 · uneditedDHCP clients with ICMP Router Discovery Protocol (IRDP) enabled allow remote attackers to modify their default routes.
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 confidenceDHCP clients with ICMP Router Discovery Protocol (IRDP) enabled are vulnerable to remote attackers sending forged router advertisement messages. Since IRDP lacks authentication, attackers can inject malicious default route entries, allowing them to intercept or redirect network traffic.
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 versions= 0a= 0ball versions= 2.6all 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Verify the installed operating system versionCheck the Windows or SunOS/Solaris version on the affected system. For Windows, use 'winver' or check System Properties. For Solaris/SunOS, use 'uname -a' or 'cat /etc/release'.Affected if The OS is Windows 2000 (any version), Windows 95 (versions 0a or 0b), Windows 98se (any version), Solaris 2.6, or SunOS (any version)
-
Confirm DHCP client is in useCheck if the system is configured to obtain IP settings via DHCP. On Windows, run 'ipconfig /all' and look for 'DHCP Enabled: Yes'. On Solaris/SunOS, check network configuration files (such as /etc/hostname.<interface> for DHCP entries) or run 'ifconfig -a' and check for DHCP-configured interfaces.Affected if The system uses DHCP to obtain IP addressing; IRDP vulnerability applies specifically to DHCP clients
-
Determine if IRDP (Router Discovery) is enabledOn Windows systems, examine the registry for IRDP-related settings. Look under HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces for values related to 'PerformRouterDiscovery' or similar IRDP configuration entries. On Solaris/SunOS, check system configuration files or use network administration commands to query router discovery settings.Affected if IRDP is enabled on the system - the vulnerability only applies when ICMP Router Discovery Protocol is active
A system is affected only if it runs one of the specified OS versions, uses DHCP for IP configuration, AND has IRDP (ICMP Router Discovery Protocol) 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 dataDisable IRDP on DHCP clients via operating system configuration (e.g., Windows registry settings or Linux kernel parameters). For enterprise environments, use Group Policy to prevent IRDP router discovery.
- 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-0875 — 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-0875 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