dbcve.org
Rapidpoint 400 FirmwareOperating system · Siemens

CVE-2018-4846

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-26
Fix available
A fix is available. Upgrade to 3.3 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
A vulnerability has been identified in RAPIDLab 1200 systems / RAPIDPoint 400 systems / RAPIDPoint 500 systems (All versions_without_ use of Siemens Healthineers Informatics products), RAPIDLab 1200 Series (All versions < V3.3 _with_ Siemens Healthineers Informatics products), RAPIDPoint 500 systems (All versions >= V3.0 _with_ Siemens Healthineers Informatics products), RAPIDPoint 500 systems (V2.4.X_with_ Siemens Healthineers Informatics products), RAPIDPoint 500 systems (All versions =< V2.3 _with_ Siemens Healthineers Informatics products), RAPIDPoint 400 systems (All versions _with_ Siemens Healthineers Informatics products). A factory account with hardcoded password might allow attackers access to the device over port 5900/tcp. Successful exploitation requires no user interaction or privileges and impacts the confidentiality, integrity, and availability of the affected device. At the time of advisory publication, no public exploitation of this security vulnerability is known. Siemens Healthineers confirms the security vulnerability and provides mitigations to resolve the security issue.

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

A hardcoded factory account with a static password exists on RAPIDLab 1200 and RAPIDPoint blood gas analyzer systems. Attackers can exploit this vulnerability over port 5900/tcp (VNC) to gain unauthorized access without any authentication or user interaction, impacting confidentiality, integrity, and availability of the affected medical devices.

MitigationImmediately restrict network access to port 5900/tcp using firewalls or network segmentation; contact Siemens Healthineers for patched firmware or credential rotation procedures specific to your device version and configuration.

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
Rapidpoint 400 FirmwareOperating system
Affected:all versions
Rapidpoint 500 FirmwareOperating system
Affected:<= 2.3>= 3.0
Rapidlab 1200 FirmwareOperating system
Affected:< 3.3

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.0/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. Identify the device model
    Locate the device nameplate or system information screen on the blood gas analyzer - look for 'RAPIDPoint 400', 'RAPIDPoint 500', or 'RAPIDLab 1200' labeling from Siemens Healthineers
    Affected if Device model is not one of these three Siemens models
  2. Check firmware version on RAPIDPoint 400
    Access the analyzer's system settings or maintenance menu to view the installed firmware version
    Affected if Device is a RAPIDPoint 400 with any firmware version (all versions affected)
  3. Check firmware version on RAPIDPoint 500
    Access the analyzer's system settings or maintenance menu to view the installed firmware version and compare to affected ranges: <= 2.3 or >= 3.0
    Affected if Device is a RAPIDPoint 500 with firmware version 2.3 or below, or version 3.0 or above
  4. Check firmware version on RAPIDLab 1200
    Access the analyzer's system settings or maintenance menu to view the installed firmware version and compare to affected range: < 3.3
    Affected if Device is a RAPIDLab 1200 with firmware version 3.2 or below
  5. Verify VNC port exposure
    Check network configuration, firewall rules, or scan port 5900/tcp from external network segments to determine if the VNC service is accessible beyond trusted segments
    Affected if Port 5900/tcp is open and accessible from untrusted network segments

A user is affected if they have a RAPIDPoint 400 (any version), RAPIDPoint 500 (<=2.3 or >=3.0), or RAPIDLab 1200 (<3.3) with VNC port 5900 exposed on an accessible network.

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
Upgrade available Upgrade to 3.3 or later
Fixed in 3.3
Interim mitigation

Immediately restrict network access to port 5900/tcp using firewalls or network segmentation; contact Siemens Healthineers for patched firmware or credential rotation procedures specific to your device version and configuration.

Fix this in Rapidpoint 400 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing32.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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