dbcve.org
Suse LinuxOperating system · Suse

CVE-2000-0800

HIGH · 10.0 CVSS v2.0 Published 2000-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
String parsing error in rpc.kstatd in the linuxnfs or knfsd packages in SuSE and possibly other Linux systems allows remote attackers to gain root privileges.

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 confidence

A string parsing error in rpc.kstatd (an NFS status daemon) in the linuxnfs or knfsd packages on SuSE and possibly other Linux systems allows remote attackers to execute arbitrary code with root privileges by sending specially crafted RPC requests to the vulnerable daemon.

MitigationIsolate or disable the vulnerable rpc.kstatd service immediately; on modern systems, ensure NFS packages are updated to current secure versions and restrict NFS access to trusted networks.

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
Suse LinuxOperating system
Affected:= 6.1= 6.2= 6.3= 6.4

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
Complete
Integrity
Complete
Availability
Complete

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

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. Identify if rpc.kstatd is running
    Run 'ps aux | grep kstatd' or 'rpcinfo -p' to list active RPC services and look for the kstatd entry
    Affected if The rpc.kstatd process is actively running on the system
  2. Check installed NFS package version
    Use the Suse package manager (rpm -qa | grep -E 'knfsd|linuxnfs') to query installed NFS-related packages and note their version strings
    Affected if The installed package version matches Suse Linux 6.1, 6.2, 6.3, or 6.4
  3. Verify RPC service exposure
    Run 'rpcinfo -p localhost' or check /etc/services for port 60001 (typical kstatd port) and use 'netstat -anp | grep 60001' to see if the service is listening on network interfaces
    Affected if rpc.kstatd is bound to a network-accessible port and accepting remote connections
  4. Confirm NFS server configuration
    Check /etc/exports and look for active NFS exports, or run 'showmount -e localhost' to see what is being shared
    Affected if NFS is enabled and exporting shares, which requires the kstatd status daemon to be active

The system is affected if it runs Suse Linux 6.1-6.4 with the knfsd or linuxnfs package installed and the rpc.kstatd daemon actively running and exposed to the 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate or disable the vulnerable rpc.kstatd service immediately; on modern systems, ensure NFS packages are updated to current secure versions and restrict NFS access to trusted networks.

Recommended fix High confidence

SUSE Linux Enterprise 15 or openSUSE Leap (migration required, not upgrade)

  1. This vulnerability affects SuSE Linux 6.1-6.4, released circa 1999-2000, which are far beyond end-of-life and no longer receive security updates.
  2. The rpc.kstatd service (knfsd/linuxnfs packages) should be disabled if still running on any legacy systems.
  3. Disable the service by removing or renaming /etc/rc.d/*kstatd* scripts and killing any running kstatd processes.
  4. Ensure firewall rules block external access to RPC services (ports 111 and 1024+).
  5. Migrate to a supported, modern Linux distribution (e.g., SUSE Linux Enterprise 15 or openSUSE Leap) as these ancient systems cannot be safely remediated.
Caveat Full system migration required; no direct upgrade path from 6.x exists; all applications and data will need to be transferred to new hardware

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Suse Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2000-0800 — 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-2000-0800 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