CVE-2018-18564
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 · uneditedAn 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, and cobas h 232 before 04.00.04 (Serial number above KQ0400000 or KS0400000). Improper access control allows attackers in the adjacent network to change the instrument configuration.
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 confidenceRoche Accu-Chek Inform II, CoaguChek Pro II, and cobas h 232 medical devices contain improper access control allowing adjacent network attackers to modify instrument configuration. The vulnerability affects specific serial number ranges across firmware versions prior to 03.06.00/04.03.00/04.00.04, enabling unauthorized configuration changes without authentication.
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< 03.06.00>= 04.00.00, < 04.03.00< 04.00.04< 04.03.00CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Roche medical device modelLocate the device label or check the device display for the model name (Accu-Chek Inform II, CoaguChek Pro II, or cobas h 232)Affected if The device is any of these three models and is running a vulnerable firmware version
-
Check the installed firmware versionAccess the device's system information menu or diagnostics screen to view the firmware version numberAffected if The firmware version is below 03.06.00, or is 04.00.00 to 04.03.00 for Accu-Chek Inform II; below 04.03.00 for CoaguChek Pro II; or below 04.00.04 for cobas h 232
-
Check the device serial number for Accu-Chek Inform IILocate the serial number on the device label or in the system configuration screenAffected if The device is Accu-Chek Inform II with serial number below 14000 and firmware below 03.06.00, or serial number 14000 and above with firmware below 04.03.00
-
Verify network exposureReview network configuration settings on the device or consult network infrastructure documentation to determine if the device is accessible from adjacent network segmentsAffected if The device is reachable from network segments beyond its immediate clinical use area, enabling adjacent network attackers to reach it
A user is affected if they have an Accu-Chek Inform II, CoaguChek Pro II, or cobas h 232 device running a firmware version within the vulnerable ranges and the device is accessible from adjacent network segments.
Generated from the published advisory. Verify against your own configuration.
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 data03.06.0004.00.0404.03.00
Apply vendor-provided firmware updates (03.06.00 for serial <14000, 04.03.00 for serial >14000 for Accu-Chek; 04.03.00 for CoaguChek Pro II; 04.00.04 for cobas h 232 serial >KQ0400000/KS0400000) and implement network segmentation to restrict adjacent network access to medical devices.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
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 locallyCheck whether your project pulls in CVE-2018-18564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-18564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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