dbcve.org
Linux KernelOperating system · Linux

CVE-2000-0344

MEDIUM · 5.0 CVSS v2.0 Published 2000-05-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
The knfsd NFS server in Linux kernel 2.2.x allows remote attackers to cause a denial of service via a negative size value.

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 · moderate confidence

The knfsd NFS server in Linux kernel 2.2.x contains a vulnerability where a remote attacker can send a request with a negative size value, causing a denial of service. This is a logic error in input validation within the NFS server daemon.

MitigationUpgrade from Linux kernel 2.2.x to a supported kernel version (3.x or later), or if running legacy systems, ensure the NFS server is not exposed to untrusted networks and consider network segmentation.

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
Linux KernelOperating system
Affected:= 2.1= 2.2.0= 2.3.0

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
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 checks

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

  1. Identify the running Linux kernel version
    Run 'uname -r' or 'cat /proc/version' to determine the installed kernel version
    Affected if The kernel version matches 2.1, 2.2.0, or 2.3.0 exactly (or falls within the 2.2.x series based on the summary indicating kernel 2.2.x is affected)
  2. Determine if the NFS server (knfsd) is enabled
    Check for nfsd processes by running 'ps aux | grep nfsd' or checking for nfsd in /proc/filesystems and looking for 'nfsd' entries in /proc/fs/
    Affected if The nfsd daemon is loaded and running on the system
  3. Verify if NFS is listening on network ports
    Run 'netstat -an | grep -E "(2049|nfs)"' or 'ss -an | grep -E "(2049|nfs)"' to check if the NFS server is bound to network interfaces
    Affected if Port 2049 (NFS) or related RPC ports are in LISTEN state and accessible over the network

The system is affected if it runs kernel version 2.1, 2.2.0, or 2.3.0 (or any 2.2.x version per the summary) AND has the NFS server daemon enabled and listening on network ports accessible to untrusted attackers.

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

Upgrade from Linux kernel 2.2.x to a supported kernel version (3.x or later), or if running legacy systems, ensure the NFS server is not exposed to untrusted networks and consider network segmentation.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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