dbcve.org
Reason Dr60 FirmwareOperating system · Ge

CVE-2021-27440

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-25
Fix available
A fix is available. Upgrade to 02a04.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
The software contains a hard-coded password it uses for its own inbound authentication or for outbound communication to external components on the Reason DR60 (all firmware versions prior to 02A04.1).

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 Reason DR60 device contains a hard-coded password embedded in its firmware, used for either inbound authentication or outbound communication to external components. This critical vulnerability (CVSS 9.8) allows attackers with network access to authenticate as a legitimate user or connect to external systems by using the known hard-coded credentials, potentially enabling full device compromise or lateral movement.

MitigationUpdate Reason DR60 firmware to version 02A04.1 or later to replace the hard-coded credentials. If immediate patching is not possible, implement network segmentation to restrict access to the device and monitor for unauthorized access attempts using the known hardcoded credentials.

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
Reason Dr60 FirmwareOperating system
Affected:< 02a04.1

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

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

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. Confirm device model
    Identify if the device is a Ge Reason DR60 by checking the device label, web interface, or SNMP inventory. The DR60 is a digital radiology workstation device.
    Affected if The device is a Ge Reason DR60 unit.
  2. Check firmware version
    Access the device's web interface, administrative console, or check via SNMP to retrieve the firmware version. Compare the version number against 02a04.1.
    Affected if The installed firmware version is less than 02a04.1 (for example, 02a04.0 or earlier).
  3. Inspect firmware for hard-coded credentials
    If firmware files are accessible (for example, via device backup, firmware update package, or TFTP dump), extract and analyze the firmware binary or configuration files for embedded password strings. Look for hard-coded credential patterns in plaintext or weakly obfuscated form.
    Affected if A hard-coded password string is found embedded in the firmware binary or configuration files.
  4. Test for default credential reuse
    Attempt to authenticate to the device using known default credentials. The hard-coded password from the firmware may be documented in security advisories or vulnerability databases.
    Affected if Authentication succeeds using the hard-coded credential, indicating the default password has not been changed.
  5. Review network exposure
    Check if the device is directly accessible from untrusted networks. Use port scans or network scans to identify open management interfaces (HTTP, HTTPS, SSH, Telnet) on the device.
    Affected if The device management interface is exposed to untrusted networks without network segmentation.

A user is affected if they have a Ge Reason DR60 device running firmware version earlier than 02a04.1 and the hard-coded password from the firmware is still in use or the device is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 02a04.1 or later
Fixed in 02a04.1
Interim mitigation

Update Reason DR60 firmware to version 02A04.1 or later to replace the hard-coded credentials. If immediate patching is not possible, implement network segmentation to restrict access to the device and monitor for unauthorized access attempts using the known hardcoded credentials.

Recommended fix High confidence

02A04.1

  1. Obtain firmware version 02A04.1 or later from Reason Technology (the vendor) through their official support channels
  2. Review the vendor's official firmware update documentation for the DR60 device
  3. Follow the vendor's prescribed procedure to upload and apply the firmware update to the device
  4. After updating, verify the device is running firmware version 02A04.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Reason Dr60 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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