dbcve.org
Service ManagerApplication · Hp

CVE-2014-2632

HIGH · 10.0 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 WebTier component in HP Service Manager (SM) 7.21 and 9.x before 9.34 allows remote attackers to execute arbitrary code 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

Unspecified vulnerability in the WebTier component of HP Service Manager allows remote attackers to execute arbitrary code. The critical CVSS score of 10 indicates complete system compromise is possible with no user interaction required.

MitigationUpgrade HP Service Manager to version 9.34 or later to remediate this vulnerability. If immediate patching is not feasible, consider restricting network access to the WebTier component as a compensating control.

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
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 checks

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

  1. Identify if HP Service Manager is installed
    Check for HP Service Manager installation directories or running processes. Common paths include C:\HP\Service Manager or /opt/HP/ServiceManager. Look for sm process or service.
    Affected if HP Service Manager software is present on the system
  2. Determine the installed version of HP Service Manager
    Check the version information in the installation directory, typically found in a version file or about dialog. Common locations: <install_dir>/version.txt or through the SMC (System Management Console) interface.
    Affected if The installed version is 7.21, 9.21, 9.30, 9.31, 9.32, or 9.33
  3. Verify the WebTier component is enabled
    Check if the WebTier (web tier) component is configured and running. This is typically accessed via web browser to the Service Manager web portal URL, or check WebTier configuration files in the webtier or tomcat subdirectory of the installation.
    Affected if WebTier component is accessible and responding to HTTP/HTTPS requests
  4. Check network exposure of the WebTier service
    Determine if the WebTier port is exposed to untrusted networks. Common ports are 8080, 8443, or 13080. Use netstat or firewall rules to identify listening interfaces and external access.
    Affected if WebTier is listening on all interfaces (0.0.0.0) or accessible from untrusted networks

A system is affected if HP Service Manager version 7.21, 9.21, 9.30, 9.31, 9.32, or 9.33 is installed with the WebTier component enabled and accessible.

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

Upgrade HP Service Manager to version 9.34 or later to remediate this vulnerability. If immediate patching is not feasible, consider restricting network access to the WebTier component as a compensating control.

Recommended fix High confidence

HP Service Manager 9.34 or later

  1. Identify the current HP Service Manager version in use
  2. Backup all critical configurations, databases, and customizations
  3. Plan and schedule the upgrade to version 9.34 or later
  4. Obtain the HP Service Manager 9.34 (or latest available) installation package from HP/HPE
  5. Follow HP's official upgrade documentation to perform the upgrade
  6. Ensure the WebTier component is also updated as part of the upgrade
  7. Verify the upgrade was successful and the WebTier is functioning correctly
Caveat Upgrading across major versions (7.x to 9.x) may require migration steps and could impact existing integrations or customizations

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

Fix this in Service Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2632 — 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-2632 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