dbcve.org
Mri 1.5t FirmwareOperating system · Philips

CVE-2021-42744

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-19
Fix available
A fix is available. Upgrade to 6.0.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Philips MRI 1.5T and MRI 3T Version 5.3 through 5.8.1 does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

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

This is an access control vulnerability in Philips MRI 1.5T and 3T systems running software versions 5.3 through 5.8.1. The device fails to properly restrict access to resources, allowing unauthorized actors to access sensitive functionality or data that should be protected.

MitigationUpgrade Philips MRI systems to a patched version beyond 5.8.1 (contact Philips for the specific fixed release). Implement network segmentation and access controls as compensating controls until the vendor patch can be applied.

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
Mri 1.5t FirmwareOperating system
Affected:>= 5.0.0, < 6.0.0
Mri 3t FirmwareOperating system
Affected:>= 5.0.0, < 6.0.0

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

CVSS:3.1/AV:L/AC:L/PR:L/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 Philips MRI system on the network
    Scan the network for Philips MRI devices using service banners, MAC OUI lookup (Philels), or by reviewing network topology diagrams and asset inventories
    Affected if The device is a Philips MRI 1.5T or 3T scanner
  2. Determine the firmware version
    Access the device service interface, system information menu, or service logs to retrieve the installed firmware version number
    Affected if The reported firmware version falls within the range >= 5.0.0 and < 6.0.0 (or software versions 5.3 through 5.8.1)
  3. Verify the software version matches vulnerable range
    Compare the extracted firmware version against the known affected ranges: 5.0.0 to 5.8.1 (versions prior to 6.0.0)
    Affected if The installed version is 5.0.0, 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x, 5.6.x, 5.7.x, 5.8.x, or 5.8.1
  4. Confirm access control configuration
    Review device access control settings, user privilege configurations, or network service configurations to determine if unauthenticated or low-privilege access is possible to sensitive functions
    Affected if The device permits access to restricted functionality without proper authentication or authorization checks

The environment is affected if the Philips MRI system (1.5T or 3T) is running firmware/software version 5.0.0 or higher but below 6.0.0, and the device exposes sensitive functions without proper access controls.

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 6.0.0 or later
Fixed in 6.0.0
Interim mitigation

Upgrade Philips MRI systems to a patched version beyond 5.8.1 (contact Philips for the specific fixed release). Implement network segmentation and access controls as compensating controls until the vendor patch can be applied.

Recommended fix Moderate confidence

Version 6.0.0 or later

  1. Contact Philips service or your authorized Philips representative to obtain the upgrade to version 6.0.0 or later
  2. Schedule maintenance window for the MRI system upgrade
  3. Ensure all patient data is backed up and system is properly shut down according to Philips procedures
  4. Apply the firmware upgrade to version 6.0.0 or later using Philips-approved upgrade process
  5. Verify the upgrade was successful and system functions normally
  6. Confirm access controls are properly configured post-upgrade
Caveat Contact Philips for specific upgrade requirements and potential compatibility considerations with existing workflows

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

Fix this in Mri 1.5t Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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