dbcve.org
Unity OrchestratorApplication · Silver Peak

CVE-2020-12145

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-05
Fix available
A fix is available. Upgrade to 8.9.11 / 8.10.11 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
Silver Peak Unity Orchestrator versions prior to 8.9.11+, 8.10.11+, or 9.0.1+ uses HTTP headers to authenticate REST API calls from localhost. This makes it possible to log in to Orchestrator by introducing an HTTP HOST header set to 127.0.0.1 or localhost. Orchestrator instances that are hosted by customers –on-premise or in a public cloud provider –are affected by this vulnerability.

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

Silver Peak Unity Orchestrator versions prior to 8.9.11+, 8.10.11+, or 9.0.1+ uses the HTTP HOST header to authenticate REST API calls originating from localhost. By setting the HOST header to 127.0.0.1 or localhost, an attacker can bypass authentication and gain unauthorized access to the Orchestrator's REST API.

MitigationUpdate Unity Orchestrator to version 8.9.11+, 8.10.11+, or 9.0.1+ or later to remediate the authentication bypass vulnerability.

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
Unity OrchestratorApplication
Affected:< 8.9.11\+>= 8.10, < 8.10.11\+>= 9.0, < 9.0.1\+

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.1/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. Confirm Unity Orchestrator presence
    Locate the Silver Peak Unity Orchestrator installation by checking for the service process or consulting system inventory. Common locations include /opt/silverpeak/ or C:\Program Files\Silver Peak\ on Windows servers.
    Affected if Unity Orchestrator is installed and running on the system
  2. Identify installed version
    Access the Unity Orchestrator web interface and navigate to the About or System Info page, or run the command 'show version' via CLI if available. The version number is typically displayed in the format x.y.z.
    Affected if The version displayed cannot be determined or is not visible
  3. Compare version to affected ranges
    Compare your installed version against these vulnerable ranges: versions < 8.9.11, versions >= 8.10.0 but < 8.10.11, versions >= 9.0.0 but < 9.0.1. Document the exact version number found in step 2.
    Affected if The installed version falls within any of these ranges: < 8.9.11, >= 8.10.0 and < 8.10.11, or >= 9.0.0 and < 9.0.1

If Unity Orchestrator is present and the installed version matches the vulnerable ranges listed, the environment is affected by CVE-2020-12145.

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 8.9.11 / 8.10.11 / 9.0.1 or later
Fixed in 8.9.118.10.119.0.1
Interim mitigation

Update Unity Orchestrator to version 8.9.11+, 8.10.11+, or 9.0.1+ or later to remediate the authentication bypass vulnerability.

Recommended fix High confidence

Upgrade to Unity Orchestrator 8.9.11+, 8.10.11+, or 9.0.1+ (depending on your current major version branch)

  1. Back up the current Unity Orchestrator configuration and data before starting the upgrade process
  2. Download the appropriate fixed version of Unity Orchestrator (8.9.11+, 8.10.11+, or 9.0.1+) from the official Silver Peak support portal at www.silver-peak.com
  3. Follow Silver Peak's standard Unity Orchestrator upgrade documentation to apply the update
  4. After upgrading, verify that HTTP-based localhost authentication restrictions are no longer in effect and that proper authentication is required for all API access
  5. Confirm the Orchestrator is functioning normally and all services are operational

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

Fix this in Unity Orchestrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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