dbcve.org
Operations ManagerApplication · Hp

CVE-2016-4373

CRITICAL · 9.8 CVSS v3.0 Published 2016-08-01
Fix available
A fix is available. Upgrade to after 9.21.120 or later.
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
The AdminUI in HPE Operations Manager (OM) before 9.21.130 on Linux, Unix, and Solaris allows remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.

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 · high confidence

This is a critical Java deserialization vulnerability in HPE Operations Manager's AdminUI where a crafted serialized Java object related to the Apache Commons Collections library allows remote attackers to execute arbitrary commands. The vulnerability stems from insecure deserialization of untrusted input.

MitigationUpgrade HPE Operations Manager to version 9.21.130 or later, or apply the vendor-provided patch. If immediate patching is not possible, restrict network access to the AdminUI interface and monitor for exploitation attempts.

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
Operations ManagerApplication
Affected:<= 9.21.120= 9.20.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 HPE Operations Manager installation
    Look for HPE Operations Manager installation directories, typically under /opt/HP or C:\Program Files\HP on Windows systems. Check for the 'AdminUI' subdirectory within the installation.
    Affected if HPE Operations Manager with AdminUI component is installed and accessible on the system.
  2. Verify AdminUI is enabled and accessible
    Confirm that the AdminUI web interface is running and exposed. Check for the AdminUI service/process and its network binding configuration.
    Affected if AdminUI service is running and accessible over the network.
  3. Determine installed Operations Manager version
    Locate version information in the installation directory, typically found in version files, About dialogs, or the AdminUI login page. Common locations include /opt/HP/OV/bin/ or similar paths under the HP installation directory.
    Affected if The installed version is 9.20.0 or any version <= 9.21.120.
  4. Check for Apache Commons Collections library
    Inspect the AdminUI application files (WAR or exploded directory) for the presence of Apache Commons Collections library JAR files in the classpath.
    Affected if Apache Commons Collections library is present in the AdminUI application files.
  5. Review network exposure of AdminUI
    Check firewall rules, service bindings, and access control lists to determine if AdminUI is exposed to untrusted networks or directly accessible from the internet.
    Affected if AdminUI is accessible from untrusted networks without proper access restrictions.

A system is affected if HPE Operations Manager version 9.20.0 or any version <= 9.21.120 is installed with AdminUI exposed and accessible, particularly over untrusted networks.

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
Upgrade available Upgrade to a release after 9.21.120
Interim mitigation

Upgrade HPE Operations Manager to version 9.21.130 or later, or apply the vendor-provided patch. If immediate patching is not possible, restrict network access to the AdminUI interface and monitor for exploitation attempts.

Recommended fix Moderate confidence

HPE Operations Manager 9.21.130 or later

  1. 1. Identify the current installed version of HPE Operations Manager by checking the version number in the AdminUI or using command-line tools
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Backup the current HPE Operations Manager configuration and data according to HPE backup procedures
  4. 4. Download HPE Operations Manager version 9.21.130 or later from the HPE support portal (support.hpe.com)
  5. 5. Stop the HPE Operations Manager services using the appropriate commands for your platform (Linux/Unix/Solaris)
  6. 6. Install the upgraded version following the HPE installation documentation for your specific platform
  7. 7. Verify the installation completed successfully and services start without errors
  8. 8. Confirm the AdminUI is accessible and the version reflects 9.21.130 or later
Caveat Review HPE release notes for version 9.21.130 for any compatibility or configuration changes before upgrading

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

Fix this in Operations Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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