CVE-2011-2398
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 dynamic loader in HP HP-UX B.11.11, B.11.23, and B.11.31 allows local users to gain privileges or cause a denial of service via unknown vectors.
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 · low confidenceVulnerability in the dynamic loader of HP-UX allows local users to escalate privileges or cause denial of service. The specific flaw and exploitation mechanism are not detailed in available sources.
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.23= b.11.31CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:S/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 confirm the installed HP-UX versionAffected if Version reported is B.11.11, B.11.23, or B.11.31 exactly (these are the affected versions)
-
Check dynamic loader file existence and permissionsInspect the dynamic loader file - typically /usr/lib/dld.so - using 'ls -la /usr/lib/dld*' and verify file attributesAffected if The dynamic loader file exists and is present on the system (the vulnerability is in this component)
-
Verify dynamic loader integrityCompare current dynamic loader files against known-good baselines or check file hashes using 'sum' or 'md5sum' if baseline hashes are availableAffected if Files show unexpected modification or differ from expected baseline values
-
Examine loader configuration filesCheck /etc/libc.ini, /etc/ldconfig, and related loader configuration files for unexpected entries using 'ls -la /etc/ld*' and review contentsAffected if Configuration files contain unexpected library paths, unauthorized modifications, or suspicious entries
-
Review system for signs of local privilege escalation attemptsCheck /var/adm/syslog or system logs for repeated failed authentication, unusual process execution, or exploit-related messages; also review audit logs if enabledAffected if Logs show evidence of privilege escalation attempts or unauthorized access to privileged processes
A system is affected if it runs HP-UX B.11.11, B.11.23, or B.11.31 and contains the vulnerable dynamic loader component - these specific versions are the definitive affected range per the CVE.
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 HP-UX B.11.11, B.11.23, and B.11.31; restrict local user access to least privilege; monitor for unauthorized changes to dynamic loader configurations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2398 — 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-2011-2398 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