# CVE-2020-12142: IPSec UDP key material can be retrieved from EdgeConnect by a user with admin credentials

> Administrators can retrieve IPSec key material via CLI or APIs, allowing decryption of in-flight communications on Silver Peak EdgeConnect devices.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g7xc-58w4-v854

## What is CVE-2020-12142?

CVE-2020-12142 is a medium-severity vulnerability in Silver Peak Systems, Inc. 1. Unity EdgeConnect, NX, VX 2. Unity Orchestrator,   3. EdgeConnect in AWS, Azure, GCP, published on 5 May 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

1. IPSec UDP key material can be retrieved from machine-to-machine interfaces and human-accessible interfaces by a user with admin credentials. Such a user, with the required system knowledge, could use this material to decrypt in-flight communication. 2. The vulnerability requires administrative access and shell access to the EdgeConnect appliance. An admin user can access IPSec seed and nonce parameters using the CLI, REST APIs, and the Linux shell.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2020-12142?

It affects 24 products.


Products: Silver-Peak Nx-1000 Firmware, Silver-Peak Nx-10k Firmware, Silver-Peak Nx-11k Firmware, Silver-Peak Nx-2000 Firmware, Silver-Peak Nx-3000 Firmware, Silver-Peak Nx-5000 Firmware, Silver-Peak Nx-6000 Firmware, Silver-Peak Nx-7000 Firmware, Silver-Peak Nx-700 Firmware, Silver-Peak Nx-8000 Firmware, Silver-Peak Nx-9000 Firmware, Silver-Peak Unity Edgeconnect for Amazon Web Services, Silver-Peak Unity Edgeconnect for Azure, Silver-Peak Unity Edgeconnect for Google Cloud Platform, Silver-Peak Unity Orchestrator, Silver-Peak Vx-1000 Firmware, Silver-Peak Vx-2000 Firmware, Silver-Peak Vx-3000 Firmware, Silver-Peak Vx-5000 Firmware, Silver-Peak Vx-500 Firmware and 4 more.

## How do I fix CVE-2020-12142?

No fix has been published for CVE-2020-12142 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-12142 being exploited?

There is no known exploitation of CVE-2020-12142 in the wild and no public exploit code.

## Other vulnerabilities in Silver Peak Systems, Inc. 1. Unity EdgeConnect, NX, VX 2. Unity Orchestrator,   3. EdgeConnect in AWS, Azure, GCP

- [CVE-2020-12143](https://insights.sbomify.com/CVE-2020-12143/): The certificate used to identify Orchestrator to EdgeConnect devices is not validated (medium 6.0)
- [CVE-2020-12144](https://insights.sbomify.com/CVE-2020-12144/): The certificate used to identify the Silver Peak Cloud Portal to EdgeConnect devices is not validated (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12142 and fix it if it is affected.

What it is: CVE-2020-12142 is a medium-severity vulnerability in Silver Peak Systems, Inc. 1. Unity EdgeConnect, NX, VX 2. Unity Orchestrator,   3. EdgeConnect in AWS, Azure, GCP, published on 5 May 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-12142 in the wild and no public exploit code.

Affected product: Silver Peak Systems, Inc. 1. Unity EdgeConnect, NX, VX 2. Unity Orchestrator,   3. EdgeConnect in AWS, Azure, GCP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-12142/ (Markdown: https://insights.sbomify.com/CVE-2020-12142/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-12142
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-12142
- OSV: https://osv.dev/vulnerability/CVE-2020-12142

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-12142/
Summaries are generated and may contain mistakes; the official description above is the record.