dbcve.org
Operations OrchestrationApplication · Hp

CVE-2017-8994

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-10
Fix available
A fix is available. Upgrade to after 10.70 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
A input validation vulnerability in HPE Operations Orchestration product all versions prior to 10.80, allows for the execution of code remotely.

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

An input validation vulnerability in HPE Operations Orchestration allows remote attackers to execute arbitrary code by submitting specially crafted input. All versions prior to 10.80 are affected, and the flaw is exploitable over the network without authentication, resulting in the critical CVSS score.

MitigationUpgrade HPE Operations Orchestration to version 10.80 or later to remediate the vulnerability. If immediate upgrading is not possible, network segmentation and restricting access to the application's input endpoints can reduce exposure until the patch can be applied.

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 OrchestrationApplication
Affected:<= 10.70

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 Orchestration installation
    Check for the presence of HPE Operations Orchestration software on the system. Common installation paths include /opt/hp/oo/ or C:\hp\oo\ on Windows. Look for the OO installation directory and theoo subfolder.
    Affected if The software is not installed - not affected. If installed, proceed to version check.
  2. Determine installed version
    Navigate to the installation directory and locate the version file or check the product version. In the OO installation folder, look for a version.properties, version.txt, or check the OO shell script (oo-version) that displays the version. The version may also be visible in the OO Central or OO Studio application about screen.
    Affected if Version is 10.70 or lower - VULNERABLE. Version is 10.80 or higher - NOT VULNERABLE.
  3. Verify network accessibility of input endpoints
    Determine if the OO web interface (OO Central) or API endpoints are accessible over the network. Check if ports 8080, 8443, or custom ports configured for OO Central are exposed externally. Review firewall rules and network configuration to confirm whether the application input endpoints can be reached remotely.
    Affected if The OO web interface or API is exposed to untrusted networks - EXPLOITABLE REMOTELY. If only accessible internally, attack surface is reduced but version remains vulnerable.
  4. Confirm authentication configuration
    Review OO security settings and authentication configuration files to determine whether the default installation allows unauthenticated access to input processing endpoints. Check if anonymous or unauthenticated access is permitted for OO Central or the OO API.
    Affected if Unauthenticated access to input endpoints is enabled - DIRECTLY EXPLOITABLE. If authentication is required, exploitation requires valid credentials.

If HPE Operations Orchestration version 10.70 or lower is installed AND the web/API interfaces are network-accessible with unauthenticated input endpoints enabled, the environment is affected by CVE-2017-8994.

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 10.70
Interim mitigation

Upgrade HPE Operations Orchestration to version 10.80 or later to remediate the vulnerability. If immediate upgrading is not possible, network segmentation and restricting access to the application's input endpoints can reduce exposure until the patch can be applied.

Recommended fix High confidence

HPE Operations Orchestration 10.80 or later

  1. 1. Back up the current HPE Operations Orchestration installation including all configurations, flows, and database data.
  2. 2. Review the HPE Operations Orchestration 10.80 release notes for upgrade prerequisites and known issues.
  3. 3. Download HPE Operations Orchestration version 10.80 or later from the HPE/HPE Software support portal.
  4. 4. Execute the upgrade installer following the official HPE upgrade documentation.
  5. 5. Verify the installation by confirming the OO version displays 10.80 or later in the product interface.
  6. 6. Validate that previously created flows and configurations function correctly after upgrade.
  7. 7. Test that the remote code execution vulnerability is no longer exploitable.
Caveat Review 10.80 release notes for any deprecated features or configuration changes that may require manual adjustments; ensure compatibility with existing integrations and dependencies before upgrading production systems.

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

Fix this in Operations Orchestration Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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