dbcve.org
AixOperating system · Ibm

CVE-1999-0111

MEDIUM · 5.0 CVSS v2.0 Published 1997-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
RIP v1 is susceptible to spoofing.

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 confidence

RIP v1 (Routing Information Protocol version 1) lacks authentication mechanisms, allowing remote attackers to inject spoofed routing updates into the network. An attacker can send fake RIP advertisements to redirect network traffic through malicious nodes or cause routing table poisoning, disrupting legitimate network communication.

MitigationMigrate from RIP v1 to RIP v2 with MD5 authentication, or transition to more secure routing protocols such as OSPF or EIGRP with appropriate authentication. Implement network segmentation to isolate RIP-enabled segments.

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
AixOperating system
Affected:= 3.2= 4.1= 4.2= 4.3

CVSS 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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check AIX version
    Run 'oslevel' to determine the installed AIX version and compare it to the affected versions (3.2, 4.1, 4.2, 4.3)
    Affected if The version matches 3.2, 4.1, 4.2, or 4.3
  2. Determine if RIP routing is enabled
    Run 'netstat -r' to view the routing table and check for RIP-specific routes, or check if the 'routed' daemon is running using 'ps -ef | grep routed'
    Affected if RIP routes appear in the routing table or the routed daemon is running
  3. Check for RIP daemon configuration
    Inspect system startup scripts (such as /etc/rc.net or /etc/rc.tcpip) for commands that start the RIP daemon (routed) without authentication flags
    Affected if The routed daemon is configured to start without authentication (RIP v1 mode)
  4. Verify network interface RIP membership
    Run 'netstat -i' or check interface configuration to see which interfaces participate in RIP routing
    Affected if Network interfaces are configured to send or receive RIP updates

You are affected if you are running AIX 3.2, 4.1, 4.2, or 4.3 AND have RIP v1 enabled and actively participating in routing updates on your network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Migrate from RIP v1 to RIP v2 with MD5 authentication, or transition to more secure routing protocols such as OSPF or EIGRP with appropriate authentication. Implement network segmentation to isolate RIP-enabled segments.

Fix this in Aix Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-1999-0111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-1999-0111 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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