CVE-2008-1662
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 · uneditedUnspecified vulnerability in the HP System Administration Manager (SAM) on HP-UX B.11.11 and B.11.23, when used to configure NFS, might allow remote attackers to read or modify arbitrary files, related to an "empty systems list."
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 confidenceHP System Administration Manager (SAM) on HP-UX B.11.11 and B.11.23 contains an unspecified vulnerability when configuring NFS with an empty systems list, allowing remote attackers to read or modify arbitrary files on the system.
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= b.11.11= b.11.23all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HP-UX versionRun 'uname -a' or 'getconf KERNEL_VERSION' to determine the HP-UX releaseAffected if The version displayed is B.11.11 or B.11.23 (or shows 11.11 or 11.23)
-
Verify SAM installationRun 'swlist -l product | grep -i sam' or 'swlist -s /var/adm/sw' to list installed SAM packagesAffected if HP System Administration Manager (SAM) is installed on the system
-
Check if SAM NFS configuration feature is usedInspect SAM configuration files in /etc or look for SAM-managed NFS exports using 'showmount -e' or check SAM log files in /var/adm/samAffected if SAM is configured to manage NFS exports or has recent NFS-related configuration entries
-
Identify empty systems list conditionReview SAM NFS configuration for any exports or share entries with empty or missing systems access lists - check /etc/dfs/dfstab or exported file systems configuration managed by SAMAffected if Any NFS export managed by SAM has an empty or unrestricted systems list that allows anonymous or arbitrary access
You are affected if running HP-UX B.11.11 or B.11.23 with SAM installed and the SAM NFS configuration feature is enabled with an empty systems list allowing unrestricted access
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 dataApply HP patches for CVE-2008-1662 if available, disable SAM NFS configuration functionality if not required, restrict network access to SAM/NFS services, or migrate away from legacy HP-UX systems.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1662 — 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-1662 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