CVE-2018-18562
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 Base Unit / Base Unit Hub before 03.01.04 and CoaguChek / cobas h232 Handheld Base Unit before 03.01.04. Weak access credentials may enable attackers in the adjacent network to gain unauthorized service access via a service interface.
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 confidenceThe vulnerability involves weak default or easily guessable credentials on the service interface of Roche Accu-Chek Inform II Base Unit, Base Unit Hub, CoaguChek, and cobas h232 Handheld Base Unit devices before version 03.01.04. Attackers with access to the adjacent network can exploit this to gain unauthorized service/administrative access to the device.
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.01.04< 03.01.04< 03.01.04< 03.01.04CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device's system information menu or service interface and locate the firmware version number. For Roche Accu-Chek Inform II, check the Base Unit settings under System > Info. For cobas h232, access via the handheld's settings menu. For CoaguChek, check the device info screen. For Base Unit Hub, check the hub status page.Affected if Firmware version is listed as anything below 03.01.04 (e.g., 03.00.00, 02.x.x)
-
Verify the service interface is accessibleAttempt to access the device's service/administrative web interface or network service port from a workstation on the same network segment. Check for open ports typically used by the device service interface.Affected if The service interface is reachable from network segments beyond the dedicated medical device network
-
Check for default credential persistenceAttempt to authenticate to the service interface using known default credential patterns for these devices (such as default service passwords found in device documentation or common factory-set credentials). Document whether authentication succeeds with any default credential combinations.Affected if Any default or easily guessable credential successfully grants access to the service/administrative interface
-
Review network configuration for service interface exposureExamine network switches, firewalls, or VLAN configurations to determine if the device's service interface is isolated from untrusted network segments or if it is accessible from general hospital/corporate network infrastructure.Affected if The device service interface is not isolated on a dedicated medical device VLAN or protected network segment
The environment is affected if any Roche Accu-Chek Inform II, cobas h232, CoaguChek, or Base Unit Hub device is running firmware below version 03.01.04 AND the service interface is accessible with default credentials.
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.01.04
Update affected devices to firmware version 03.01.04 or later and change all default credentials to strong, unique values. Restrict network access to the service interface to minimize attack surface.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18562 — 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-18562 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