dbcve.org
Dmc 3000 FirmwareOperating system · Mirion Technologies

CVE-2017-9649

MEDIUM · 5.0 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 →
55/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
A Use of Hard-Coded Cryptographic Key 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). An unchangeable, factory-set key is included in the 900 MHz transmitter firmware.

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 firmware in Mirion Technologies radiation monitoring devices (DMC 3000, iPam, RDS-31 iTX, DRM-1/2, Telepole II, MESH Repeater) contains a hard-coded, unchangeable 900 MHz transmitter key used to secure radio communications. An attacker who discovers this factory-set key could potentially decrypt, spoof, or manipulate telemetry data transmitted between devices.

MitigationContact Mirion Technologies for firmware updates that implement proper key management; until available, isolate affected devices on restricted networks and monitor for unauthorized radio interference. The hard-coded key cannot be changed by operators.

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 FirmwareOperating system
Affected:all versions
Ipam Transmitter F\/dmc 2000 FirmwareOperating system
Affected:all versions
Telepole Ii FirmwareOperating system
Affected:all versions
Rds 31 Itx FirmwareOperating system
Affected:all versions
Rsd31 Am FirmwareOperating system
Affected:all versions
Wrm2 Mesh Repeater FirmwareOperating system
Affected:all versions
Drm 1\/2 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 your network
    Scan network for devices with manufacturer OUI (Organizationally Unique Identifier) or review asset inventory for Mirion Technologies products. Common device types include DMC 3000, iPam, RDS-31 iTX, DRM-1/2, Telepole II, and WRM2 Mesh Repeater.
    Affected if Any Mirion Technologies radiation monitoring device from the listed models is present on the network
  2. Confirm device model and radio module
    Access the device management interface or CLI and identify the exact model number and whether the 900 MHz radio transmitter module is installed and enabled.
    Affected if Device is one of: DMC 3000, iPam/DMC 2000, Telepole II, RDS-31 iTX, RDS-31 AM, WRM2 Mesh Repeater, or DRM-1/2 with 900 MHz radio enabled
  3. Verify radio communication status
    Check device configuration for active 900 MHz telemetry transmission. Look for settings related to RF transmission, radio link status, or telemetry output on the 900 MHz frequency band.
    Affected if Device is actively transmitting data over 900 MHz radio frequencies
  4. Assess network exposure of affected devices
    Review firewall rules and network segmentation to determine if these devices are isolated from untrusted networks or directly accessible from external networks.
    Affected if Mirion radio-enabled devices are reachable from networks outside your operational/isolated zone

You are affected if you have any Mirion Technologies DMC 3000, iPam, RDS-31 iTX, DRM-1/2, Telepole II, or WRM2 Mesh Repeater devices with 900 MHz radio transmission enabled, regardless of firmware version since all versions contain the hard-coded key.

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 that implement proper key management; until available, isolate affected devices on restricted networks and monitor for unauthorized radio interference. The hard-coded key cannot be changed by operators.

Fix this in Dmc 3000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9649 — 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-9649 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