CVE-2020-12146
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 · uneditedIn Silver Peak Unity Orchestrator versions prior to 8.9.11+, 8.10.11+, or 9.0.1+, an authenticated user can access, modify, and delete restricted files on the Orchestrator server using the/debugFiles REST API.
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 confidenceA directory traversal and improper authorization vulnerability in the /debugFiles REST API of Silver Peak Unity Orchestrator allows any authenticated user to read, modify, and delete arbitrary files on the server file system, bypassing intended access controls.
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< 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionAccess the Silver Peak Unity Orchestrator management interface and navigate to the About or System Information page to view the exact firmware version number.Affected if Version is < 8.9.11, or between 8.10.0 and 8.10.10 inclusive, or between 9.0.0 and 9.0.0 inclusive (all pre-patch versions)
-
Verify the debugFiles REST API endpoint existsSend an HTTP request to the /debugFiles endpoint on the Unity Orchestrator (e.g., GET https://<orchestrator-ip>/debugFiles) and observe if the endpoint responds.Affected if The endpoint responds with any HTTP status code, indicating it is accessible and likely vulnerable on unpatched versions
-
Confirm authentication is enabled for the management interfaceCheck the Unity Orchestrator user authentication settings under the Administration or Security section to verify that user authentication is required for API access.Affected if Authentication is required - the vulnerability allows any authenticated user to exploit the directory traversal, so the presence of any user accounts increases exploitability
-
Check network accessibility of management interfaceDetermine if the Unity Orchestrator management port (typically 443) is accessible from untrusted networks by reviewing firewall rules or performing a port scan from an external IP.Affected if The management interface is exposed to the internet or untrusted networks, increasing the likelihood of exploitation
If the product is Silver Peak Unity Orchestrator with a version falling in the affected ranges AND the /debugFiles endpoint is accessible, the environment is vulnerable to CVE-2020-12146.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data8.9.118.10.119.0.1
Update Silver Peak Unity Orchestrator to version 8.9.11+, 8.10.11+, or 9.0.1+ (or later) to patch the vulnerable debugFiles endpoint. Alternatively, restrict network access to the management interface and enforce least-privilege user accounts until the patch can be applied.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-12146 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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