CVE-2007-0915
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 · uneditedDistributed SLS daemon (SLSd) on HP-UX B.11.11 allows remote attackers to overwrite arbitrary files and gain privileges via a crafted RPC 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 · moderate confidenceThe Distributed SLS daemon (SLSd) on HP-UX B.11.11 contains a vulnerability where remote attackers can send crafted RPC requests to overwrite arbitrary files on the system, enabling privilege escalation to root or administrator-level 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 data= 11.11CVSS 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.
-
Verify HP-UX versionRun 'uname -a' or 'swlist -l bundle' to confirm the HP-UX version is B.11.11Affected if The system is running HP-UX B.11.11 specifically
-
Check if SLSd is installedRun 'swlist -l product | grep -i SLS' or 'ps -ef | grep slsd' to see if the SLS daemon package is installed and runningAffected if SLSd package is installed and the slsd process is running
-
Verify RPC listener statusRun 'rpcinfo -p' to check if the program number used by SLSd (consult SLSd documentation for specific program number) is registered and listening on RPC port 111Affected if SLSd is registered as an RPC service and listening on the network
-
Check network exposure of RPC portRun 'netstat -an | grep :111' or use 'nmap -sT -p 111 <target>' to determine if port 111 (sunrpc) is bound to a network interface accessible from remote systemsAffected if RPC port 111 is bound to a non-loopback interface and accessible from remote networks
A user is affected if they are running HP-UX 11.11 with the SLSd RPC service enabled and exposed to network access, allowing remote attackers to potentially escalate privileges 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 dataThis vulnerability affects an End-of-Life HP-UX 11.11 system; primary remediation is to migrate to a supported platform. If the SLSd service is not required, disable it immediately. Otherwise, restrict network access to the RPC port via firewall or ACLs to prevent unauthenticated remote exploitation.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0915 — 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-2007-0915 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