Nfs UtilsApplication · Redhat
CVE-2008-1376
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 · uneditedA certain Red Hat build script for nfs-utils before 1.0.9-35z.el5_2 on Red Hat Enterprise Linux (RHEL) 5 omits TCP wrappers support, which might allow remote attackers to bypass intended access restrictions.
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 confidenceThis vulnerability exists in a Red Hat build script for nfs-utils that omitted TCP wrappers support during the build process. Without TCP wrappers compiled in, the NFS service does not respect access controls configured in hosts.allow/hosts.deny, potentially allowing remote attackers to bypass intended network access restrictions.
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
Nfs UtilsApplication
= 1.0.9CVSS 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.
-
Check installed nfs-utils versionRun: rpm -q nfs-utils (on RHEL/RHEL-based systems)Affected if Version is 1.0.9 (exact match) or earlier without the -35z.el5_2 or later patch level
-
Verify TCP wrappers library linkageRun: ldd /usr/sbin/rpc.nfsd 2>/dev/null | grep -i wrap (or check for libwrap.so in the binary)Affected if The libwrap library is not present in the linked libraries, indicating TCP wrappers support was not compiled in
-
Check if hosts.allow/hosts.deny controls existInspect /etc/hosts.allow and /etc/hosts.deny for NFS-related entries (look for rpc.nfsd, nfsd, or portmap entries)Affected if Access controls are configured in hosts.allow/hosts.deny but the nfs-utils binary lacks TCP wrappers support, making those controls ineffective
-
Confirm NFS service is running and exposedRun: rpcinfo -p | grep -E 'nfs|mountd' to verify NFS services are registered and accessible on the networkAffected if NFS services are running and exposed on the network while TCP wrappers support is absent, allowing potential bypass of host-based access controls
You are affected if nfs-utils version 1.0.9 is installed without the -35z.el5_2 patch, TCP wrappers support is not compiled into the NFS binaries, and host-based access controls in hosts.allow/hosts.deny are configured but not being enforced.
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 dataUpdate nfs-utils to version 1.0.9-35z.el5_2 or later on affected RHEL 5 systems to restore TCP wrappers support and ensure NFS access controls are properly enforced.
Fix this in Nfs Utils
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1376 — 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-2008-1376 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