CVE-2011-1860
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 HP Service Manager 7.02, 7.11, 9.20, and 9.21 and Service Center 6.2.8 allows remote attackers to capture HTTP session credentials 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 · moderate confidenceHP Service Manager and Service Center contain an unspecified vulnerability allowing remote attackers to capture HTTP session credentials. The vulnerability is network-exploitable without authentication and results in partial confidentiality impact.
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= 6.2.8= 7.02= 7.11= 9.20= 9.21CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 installed HP Service Manager or Service Center productLocate the HP Service Manager or Service Center installation directory or check system inventory/asset management tools for these applicationsAffected if The product is HP Service Manager or Service Center
-
Determine the exact version of HP Service ManagerCheck the product's about dialog, version file, or run: sm -version (typically in the installation bin directory)Affected if Version equals 7.02, 7.11, 9.20, or 9.21
-
Determine the exact version of HP Service CenterCheck the product's about dialog, version file, or check installation logs/documentationAffected if Version equals 6.2.8
-
Verify HTTP session exposureCheck if the web interface (typically ports 13080, 13000, or similar) is accessible from untrusted networks or the internetAffected if The HTTP interface is network-accessible without additional security controls
-
Check for session security controlsReview configuration files (typically in the SM or SC installation conf directory) for session binding, token rotation settings, or IP validation settingsAffected if No additional session security controls are configured and the affected version is detected
You are affected if HP Service Manager version 7.02, 7.11, 9.20, or 9.21 OR HP Service Center version 6.2.8 is installed and the HTTP session interface is network-accessible without protective controls.
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 vendor patches or upgrades to HP Service Manager (to version 9.31+) and Service Center. If patches are unavailable, implement additional session security controls such as IP binding, session token rotation, and forced re-authentication for sensitive operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1860 — 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-1860 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