CVE-2001-0266
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 · uneditedVulnerability in Software Distributor SD-UX in HP-UX 11.0 and earlier allows local users to gain 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 · moderate confidenceThis is a local privilege escalation vulnerability in HP-UX 11.0 and earlier systems affecting the Software Distributor (SD-UX) component. The vulnerability allows unprivileged local users to gain elevated (root) privileges by exploiting improper access controls or input validation in the SD-UX software. The CVSS base score of 7.2 indicates significant impact with complete confidentiality, integrity, and availability compromise possible.
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<= 11.00CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 the HP-UX versionRun `uname -a` or `swlist -a version` to determine the installed HP-UX versionAffected if The version is 11.00 or earlier (e.g., 10.x, 9.x)
-
Verify if SD-UX is installedRun `swlist | grep -i sd` or `swlist -a product` to list installed SD-UX (Software Distributor) packagesAffected if SD-UX (software distributor) package is present on the system
-
Check SD-UX daemon statusVerify if the SD-UX service or daemon is running using `ps -ef | grep sd` or check for the presence of SD-UX binaries in /usr/sbin/Affected if SD-UX daemon or related processes are active
-
Review SD-UX file permissionsInspect permissions on SD-UX executables and configuration files in /var/opt/sd and /opt/sd directories using `ls -la`Affected if Unprivileged users have read or execute access to sensitive SD-UX binaries or config files
-
Confirm user access to SD-UX commandsAttempt to execute SD-UX commands as a non-root user (e.g., `sd`) to verify if the component is accessible to unprivileged accountsAffected if Unprivileged users can invoke SD-UX utilities or access the component
A system is affected if it runs HP-UX version 11.00 or earlier with SD-UX installed and accessible to unprivileged local users, enabling potential privilege escalation to root.
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 the appropriate HP patch for SD-UX or upgrade to a supported HP-UX version if patches are unavailable. If SD-UX is not required in production, consider disabling or removing the component to reduce the attack surface.
- 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-2001-0266 — 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-2001-0266 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