# CVE-2020-1688: Junos OS: SRX and NFX Series: Insufficient Web API private key protection

> A local authenticated user can obtain the Web API private key, allowing decryption of communications between the device and authenticator services.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cccx-r256-72j4

## What is CVE-2020-1688?

CVE-2020-1688 is a medium-severity vulnerability in Juniper Junos, published on 16 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Juniper Networks SRX Series and NFX Series, a local authenticated user with access to the shell may obtain the Web API service private key that is used to provide encrypted communication between the Juniper device and the authenticator services. Exploitation of this vulnerability may allow an attacker to decrypt the communications between the Juniper device and the authenticator service. This Web API service is used for authentication services such as the Juniper Identity Management Service, used to obtain user identity for Integrated User Firewall feature, or the integrated ClearPass authentication and enforcement feature. This issue affects Juniper Networks Junos OS on Networks SRX Series and NFX Series: 12.3X48 versions prior to 12.3X48-D105; 15.1X49 versions prior to 15.1X49-D190; 16.1 versions prior to 16.1R7-S8; 17.2 versions prior to 17.2R3-S4; 17.3 versions prior to 17.3R3-S8; 17.4 versions prior to 17.4R2-S11, 17.4R3; 18.1 versions prior to 18.1R3-S7; 18.2 versions prior to 18.2R3; 18.3 versions prior to 18.3R2-S4, 18.3R3; 18.4 versions prior to 18.4R1-S7, 18.4R2; 19.1 versions prior to 19.1R2; 19.2 versions prior to 19.2R1-S4, 19.2R2.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor), CWE-522 (Insufficiently Protected Credentials), CWE-320

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2020-1688 being exploited?

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

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1688 is a medium-severity vulnerability in Juniper Junos, published on 16 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1688 in the wild and no public exploit code.

Affected product: Juniper Junos. 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-1688/ (Markdown: https://insights.sbomify.com/CVE-2020-1688/index.md)
```

## Sources

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

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