dbcve.org
Accu Chek Inform Ii FirmwareOperating system · Roche

CVE-2018-18563

CRITICAL · 9.6 CVSS v3.0 Published 2018-11-20
Fix available
A fix is available. Upgrade to 03.01.03 / 03.01.06 or later.
See remediation →
100/100
Remediation priority · Urgent
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 issue was discovered in Roche Accu-Chek Inform II Instrument before 03.06.00 (Serial number below 14000) and 04.x before 04.03.00 (Serial Number above 14000), CoaguChek Pro II before 04.03.00, CoaguChek XS Plus before 03.01.06, CoaguChek XS Pro before 03.01.06, cobas h 232 before 03.01.03 (Serial Number below KQ0400000 or KS0400000) and cobas h 232 before 04.00.04 (Serial Number above KQ0400000 or KS0400000). Improper access control to a service command allows attackers in the adjacent network to execute arbitrary code on the system through a crafted Poct1-A message.

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

This is an improper access control vulnerability in multiple Roche point-of-care testing devices. A service command lacks proper authentication, allowing attackers on the adjacent network to send crafted Poct1-A protocol messages and execute arbitrary code. The vulnerability affects specific firmware versions across Accu-Chek Inform II, CoaguChek Pro II, CoaguChek XS Plus, CoaguChek XS Pro, and cobas h 232 devices based on serial number ranges.

MitigationApply vendor-supplied firmware updates to the patched versions (Accu-Chek Inform II 03.06.00/04.03.00, CoaguChek Pro II 04.03.00, CoaguChek XS Plus/Pro 03.01.06, cobas h 232 03.01.03/04.00.04). Additionally, implement network segmentation to restrict the adjacent network attack surface and monitor for unauthorized Poct1-A messages.

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
Accu Chek Inform Ii FirmwareOperating system
Affected:< 03.06.00>= 04.00.00, < 04.03.00
Cobas H 232 FirmwareOperating system
Affected:< 03.01.03>= 04.00.00, < 04.00.04
Coaguchek Pro Ii FirmwareOperating system
Affected:< 04.03.00
Coaguchek Xs Plus FirmwareOperating system
Affected:< 03.01.06
Coaguchek Xs Pro FirmwareOperating system
Affected:< 03.01.06

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/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 Roche POC device model
    Locate the physical device or check inventory records for Roche point-of-care testing equipment. The affected models are: Accu-Chek Inform II, CoaguChek Pro II, CoaguChek XS Plus, CoaguChek XS Pro, and cobas h 232. Verify the exact model name and serial number.
    Affected if The device is one of the five affected models listed in the CVE.
  2. Determine the installed firmware version
    Access the device's system information menu or use the manufacturer's service interface to retrieve the firmware version. For Accu-Chek Inform II, this is typically found in Settings > System > Device Info. For cobas h 232, check under Maintenance > Software Version. Compare the version number against the affected ranges.
    Affected if The firmware version falls within any of these ranges: Accu-Chek Inform II < 03.06.00 or >= 04.00.00 and < 04.03.00; cobas h 232 < 03.01.03 or >= 04.00.00 and < 04.00.04; CoaguChek Pro II < 04.03.00; CoaguChek XS Plus < 03.01.06; CoaguChek XS Pro < 03.01.06.
  3. Verify Poct1-A protocol configuration
    Check the device network settings or communication configuration to confirm whether the Poct1-A protocol service is enabled. This is typically found in the device's connectivity or interface settings menu. The vulnerability requires this protocol to be active for exploitation.
    Affected if The Poct1-A protocol service is enabled and accessible on the device.
  4. Assess network exposure
    Review network segmentation and firewall rules to determine if the device is on an adjacent network that could be accessed by untrusted parties. Check if the device's communication ports (particularly those used by Poct1-A) are reachable from network segments outside the clinical network.
    Affected if The device is on a network segment accessible to untrusted users or systems, allowing adjacent network attackers to reach the Poct1-A service.

A user is affected if their device is one of the five Roche POC models AND the firmware version is below the patched versions AND Poct1-A protocol is enabled AND the device is reachable from an adjacent 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.

dbcve · scoped
Upgrade available Upgrade to 03.01.03 / 03.01.06 / 03.06.00 or later
Fixed in 03.01.0303.01.0603.06.00
Interim mitigation

Apply vendor-supplied firmware updates to the patched versions (Accu-Chek Inform II 03.06.00/04.03.00, CoaguChek Pro II 04.03.00, CoaguChek XS Plus/Pro 03.01.06, cobas h 232 03.01.03/04.00.04). Additionally, implement network segmentation to restrict the adjacent network attack surface and monitor for unauthorized Poct1-A messages.

Recommended fix High confidence

Accu-Chek Inform II: 03.06.00 (SN<14000) or 04.03.00 (SN>=14000); CoaguChek Pro II: 04.03.00; CoaguChek XS Plus/Pro: 03.01.06; cobas h 232: 03.01.03 (SN<KQ/KS0400000) or 04.00.04 (SN>=KQ/KS0400000)

  1. 1. Identify the exact model and serial number of the Roche medical device (Accu-Chek Inform II, CoaguChek Pro II, CoaguChek XS Plus, CoaguChek XS Pro, or cobas h 232)
  2. 2. Contact Roche Diagnostics technical support to obtain the official firmware upgrade
  3. 3. Request firmware version 03.06.00 or higher for Accu-Chek Inform II (serial <14000)
  4. 4. Request firmware version 04.03.00 or higher for Accu-Chek Inform II (serial >=14000)
  5. 5. Request firmware version 04.03.00 or higher for CoaguChek Pro II
  6. 6. Request firmware version 03.01.06 or higher for CoaguChek XS Plus
  7. 7. Request firmware version 03.01.06 or higher for CoaguChek XS Pro
  8. 8. For cobas h 232: Request firmware 03.01.03 or higher (serial <KQ0400000/KS0400000) or 04.00.04 or higher (serial >=KQ0400000/KS0400000)
Caveat Firmware upgrades on medical devices may require recalibration, validation, or reconfiguration; coordinate with Roche service and follow facility change control procedures

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

Fix this in Accu Chek Inform Ii Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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