Enterprise LinuxOperating system · Redhat

CVE-2004-0946

HIGH · 10.0 CVSS v2.0 Published 2005-01-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
rquotad in nfs-utils (rquota_server.c) before 1.0.6-r6 on 64-bit architectures does not properly perform an integer conversion, which leads to a stack-based buffer overflow and allows remote attackers to execute arbitrary code via a crafted NFS request.

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

A detailed technical summary for this CVE is being prepared.

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
Enterprise LinuxOperating system
Affected:= 3.0
Enterprise Linux DesktopOperating system
Affected:= 3.0
Nfs UtilsApplication
Affected:= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.6

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

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
Patch available Apply the vendor patch
Vendor patch www.gentoo.org →
Recommended fix High confidence

nfs-utils version 1.0.6-r6 or later, or equivalent patched version from Red Hat Enterprise Linux 3.0 errata

  1. Identify the nfs-utils package version currently installed (e.g., using 'rpm -qa | grep nfs-utils' or 'dpkg -l | grep nfs-utils')
  2. For Red Hat Enterprise Linux 3.0 systems, obtain the updated nfs-utils package from Red Hat's errata or update channels for RHEL 3.0
  3. Apply the update using the appropriate package manager (e.g., 'up2date nfs-utils' or 'yum update nfs-utils' or download and install the RPM manually)
  4. Verify the updated version is 1.0.6-r6 or later, or contains the CVE-2004-0946 fix
  5. Restart the rquotad service if it is running (e.g., '/etc/init.d/rpc.rquotad restart' or 'service rpc-rquotad restart')
  6. Confirm the service is listening on the appropriate port (typically 20011) and functioning correctly
Caveat Upgrading nfs-utils may require service restart; test in non-production environment first to ensure compatibility with NFS client configurations

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-0946 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-0946 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