dbcve.org
Dmc 3000 Transmitter FirmwareOperating system · Mirion

CVE-2017-9645

MEDIUM · 6.5 CVSS v3.0 Published 2017-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

The Mirion Technologies radiation monitoring telemetry devices (DMC 3000, iPam, RDS-31 iTX, DRM-1/2, and related units) use inadequate encryption that allows decryption of data at the hardware level. This vulnerability exposes sensitive radiation monitoring data transmitted wirelessly from these industrial safety devices.

MitigationContact Mirion Technologies for firmware updates or hardware replacement to address the weak encryption. Implement compensating network controls (network segmentation, VPN tunnels) to protect telemetry data in transit until proper encryption patches are available.

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
Dmc 3000 Transmitter FirmwareOperating system
Affected:all versions
Ipam Transmitter F\/dmc 2000 FirmwareOperating system
Affected:all versions
Rds 31 Itx FirmwareOperating system
Affected:all versions
Drm 1\/2 FirmwareOperating system
Affected:all versions
Drm 2 FirmwareOperating system
Affected:all versions
Rds 31 FirmwareOperating system
Affected:all versions
Telepole 2 FirmwareOperating system
Affected:all versions
Wrm2 FirmwareOperating system
Affected:all versions

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mirion radiation monitoring devices on the network
    Scan network inventory or conduct device discovery to find Mirion telemetry hardware such as DMC 3000, iPam, RDS-31 iTX, DRM-1, DRM-2, Telepole 2, or WRM2 units. Check device nameplates, management interfaces, or asset inventories for these model numbers.
    Affected if Any Mirion DMC 3000, iPam, RDS-31 iTX, DRM-1/2, Telepole 2, or WRM2 transmitter device is present in the environment.
  2. Confirm device firmware version
    Access the device management interface or check the firmware version reported by the device. Compare the installed firmware version against the affected product list.
    Affected if The device firmware matches any Mirion product listed in the affected products (DMC 3000, iPam, RDS-31 iTX, DRM-1, DRM-2, RDS-31, Telepole 2, WRM2) regardless of version.
  3. Verify wireless telemetry is enabled
    Check device configuration settings or network traffic to determine if the device is transmitting radiation monitoring data wirelessly. Look for RF transmission indicators or telemetry output configuration in the device management console.
    Affected if Wireless telemetry transmission is enabled and actively sending data from the affected device.
  4. Inspect telemetry encryption configuration
    Examine the data stream or device encryption settings to determine whether the telemetry data is protected by weak or inadequate encryption. This may require capturing and analyzing the wireless signal or reviewing encryption parameters in the device settings.
    Affected if The telemetry data is transmitted without encryption or with known weak encryption methods that allow decryption at the hardware level.

If Mirion radiation monitoring devices (DMC 3000, iPam, RDS-31 iTX, DRM-1/2, Telepole 2, or WRM2) are present and transmitting wireless telemetry data with inadequate encryption, the environment is affected by CVE-2017-9645.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact Mirion Technologies for firmware updates or hardware replacement to address the weak encryption. Implement compensating network controls (network segmentation, VPN tunnels) to protect telemetry data in transit until proper encryption patches are available.

Fix this in Dmc 3000 Transmitter Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9645 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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