# CVE-2017-9645: Weak cryptography in Mirion Technologies Telemetry Enabled Devices

> Attackers can decrypt data at the hardware level in Mirion Technologies telemetry devices due to inadequate encryption strength.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wp56-rp8w-8p9w

## What is CVE-2017-9645?

CVE-2017-9645 is a medium-severity vulnerability in Mirion Technologies Telemetry Enabled Devices, published on 20 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Inadequate Encryption Strength issue was discovered in Mirion Technologies DMC 3000 Transmitter Module, iPam Transmitter f/DMC 2000, RDS-31 iTX and variants (including RSD31-AM Package), DRM-1/2 and variants (including Solar PWR Package), DRM and RDS Based Boundary Monitors, External Transmitters, Telepole II, and MESH Repeater (Telemetry Enabled Devices). Decryption of data is possible at the hardware level.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 8 products.


Products: Mirion Dmc 3000 Transmitter Firmware, Mirion Drm-1\/2 Firmware, Mirion Drm-2 Firmware, Mirion Ipam Transmitter F\/Dmc 2000 Firmware, Mirion Rds-31 Firmware, Mirion Rds-31 Itx Firmware, Mirion Telepole 2 Firmware, Mirion Wrm2 Firmware.

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

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

## Is CVE-2017-9645 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9645 is a medium-severity vulnerability in Mirion Technologies Telemetry Enabled Devices, published on 20 Sep 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-9645 in the wild and no public exploit code.

Affected product: Mirion Technologies Telemetry Enabled Devices. 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-9645/ (Markdown: https://insights.sbomify.com/CVE-2017-9645/index.md)
```

## Sources

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

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