# CVE-2017-10606: SRX Series: Cryptographic weakness in SRX300 Series TPM Firmware

> Weak cryptographic key generation in SRX300 TPM firmware allows attackers to decrypt sensitive configuration data.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-h472-275m-5q88

## What is CVE-2017-10606?

CVE-2017-10606 is a medium-severity vulnerability in Juniper Networks Junos OS, published on 13 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Version 4.40 of the TPM (Trusted Platform Module) firmware on Juniper Networks SRX300 Series has a weakness in generating cryptographic keys that may allow an attacker to decrypt sensitive information in SRX300 Series products. The TPM is used in the SRX300 Series to encrypt sensitive configuration data. While other products also ship with a TPM, no other products or platforms are affected by this vulnerability. Customers can confirm the version of TPM firmware via the 'show security tpm status' command. This issue was discovered by an external security researcher. No other Juniper Networks products or platforms are affected by this issue.

## Which versions are affected by CVE-2017-10606?

It affects 1 product.


Products: Juniper Trusted Platform Module Firmware.

## How do I fix CVE-2017-10606?

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

## Is CVE-2017-10606 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10606 and fix it if it is affected.

What it is: CVE-2017-10606 is a medium-severity vulnerability in Juniper Networks Junos OS, published on 13 Oct 2017. 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-2017-10606 in the wild and no public exploit code.

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

## Sources

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

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