CVE-1999-0127
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 · uneditedswinstall and swmodify commands in SD-UX package in HP-UX systems allow local users to create or overwrite arbitrary files to gain root access.
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 confidenceThe swinstall and swmodify commands in HP-UX's SD-UX (Software Distributor) package contain a privilege escalation vulnerability allowing local authenticated users to create or overwrite arbitrary files on the system, potentially leading to root access.
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 dataall 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
- 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.
-
Confirm system is HP-UXRun 'uname -a' or 'uname -sr' to verify the operating system is HP-UXAffected if System is not HP-UX (not affected)
-
Verify SD-UX package is installedRun 'swlist -l product' or 'swlist -s | grep -i sd-ux' to list installed software products and check for SD-UX (Software Distributor)Affected if SD-UX is not installed on the system
-
Check if swinstall command existsRun 'which swinstall' or 'ls -la /usr/sbin/swinstall' to locate the swinstall binaryAffected if swinstall command does not exist (not vulnerable)
-
Check if swmodify command existsRun 'which swmodify' or 'ls -la /usr/sbin/swmodify' to locate the swmodify binaryAffected if swmodify command does not exist (not vulnerable)
-
Inspect permissions on swinstall and swmodifyRun 'ls -la /usr/sbin/swinstall /usr/sbin/swmodify' and check if non-privileged users have execute permission or write access to these binariesAffected if Non-privileged users can execute these commands (vulnerable condition present)
The environment is affected if running HP-UX with SD-UX installed and the swinstall or swmodify commands are accessible to local authenticated non-root users.
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 SD-UX from 1999 or later; restrict execution permissions on swinstall/swmodify to authorized administrators only; consider removing SD-UX if not required on systems where it's not needed.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0127 — 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-1999-0127 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