dbcve.org
Service ManagerApplication · Hp

CVE-2014-2634

HIGH · 9.4 CVSS v2.0 Published 2014-08-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in the server in HP Service Manager (SM) 7.21 and 9.x before 9.34 allows remote attackers to bypass intended access restrictions, and modify data 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 · moderate confidence

HP Service Manager versions 7.21 and 9.x before 9.34 contain an unspecified server-side vulnerability allowing remote attackers to bypass access controls and modify data or cause denial of service. The nature of the bypass suggests a privilege escalation or authentication bypass flaw in the web/application server layer.

MitigationApply HP Service Manager version 9.34 or later to address the access restriction bypass. Verify system integrity post-patch and review access logs for indicators of exploitation prior to patching.

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
Service ManagerApplication
Affected:= 7.21= 9.21= 9.30= 9.31= 9.32= 9.33

CVSS 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
None
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed HP Service Manager version
    Locate the version information for your HP Service Manager installation. Check the SM server configuration, About dialog, or version file typically found in the installation directory. Common locations include the sm.ini file, registry entries on Windows, or the 'sm -version' command if accessible.
    Affected if The installed version is 7.21 or any 9.x version below 9.34 (such as 9.21, 9.30, 9.31, 9.32, or 9.33)
  2. Confirm web/application server tier is in use
    Verify that the HP Service Manager web tier or application server component is deployed and active. This includes the SM Web Client, SM Servlet Engine, or third-party web server (IIS, Apache) configured to serve HP Service Manager pages.
    Affected if The web/application server tier is enabled and accessible, as the vulnerability exploits the web layer to bypass access controls
  3. Check for unauthorized access attempts
    Review access logs, security logs, and audit trails for the HP Service Manager web tier. Look for unusual requests, privilege escalation patterns, or operations performed by users without proper role permissions occurring around the timeframe of potential exploitation.
    Affected if Logs show actions performed with elevated privileges or access to functions that should be restricted for the authenticating user's role

You are affected if HP Service Manager version 7.21 or any 9.x version below 9.34 is installed and the web/application server tier is exposed, as this enables the access control bypass vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply HP Service Manager version 9.34 or later to address the access restriction bypass. Verify system integrity post-patch and review access logs for indicators of exploitation prior to patching.

Recommended fix High confidence

HP Service Manager 9.34 or later (contact HP/HPE for 7.x line upgrade options)

  1. Verify current HP Service Manager version by checking the server or using SM version commands
  2. Schedule a maintenance window for the upgrade
  3. Back up the Service Manager database and configuration files
  4. Upgrade to HP Service Manager version 9.34 or later (for 9.x installations)
  5. For version 7.21, contact HP/HPE for upgrade options to a supported release
  6. After upgrade, verify the server starts successfully and test critical functions
  7. Review audit logs to confirm no unauthorized access occurred prior to the upgrade
Caveat Review release notes for 9.34+ for any changes to APIs, integrations, or workflows that may affect existing configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Service Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2634 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2634 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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