CVE-2017-12722
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 Out-of-bounds Read issue was discovered in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump, Version 1.1, 1.5, and 1.6. A third-party component used in the pump reads memory out of bounds, causing the communications module to crash. Smiths Medical assesses that the crash of the communications module would not impact the operation of the therapeutic module.
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 confidenceAn out-of-bounds read vulnerability exists in a third-party component of the Medfusion 4000 Wireless Syringe Infusion Pump. The vulnerability allows the component to read memory beyond allocated boundaries, causing the communications module to crash. While this affects device communications, Smiths Medical states the therapeutic module (infusion delivery) remains unaffected.
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= 1.1= 1.5= 1.6CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Confirm device modelIdentify the exact model of the infusion pump in your environment. Verify it is the Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump by checking the device label, inventory records, or network discovery scans.Affected if The device is a Medfusion 4000 Wireless Syringe Infusion Pump
-
Check installed firmware versionAccess the device settings or diagnostic interface to retrieve the current firmware/software version. This is typically found in the device's system information, maintenance menu, or through the clinical interface. Compare the version number against the affected versions.Affected if The firmware version is exactly 1.1, 1.5, or 1.6
-
Verify communications module is activeDetermine whether the wireless communications module is enabled and actively used for remote monitoring or network connectivity. Check device configuration settings or network connection status.Affected if The communications module is enabled and the device is networked
-
Monitor for communications crashesReview device logs, network monitoring tools, or centralized monitoring systems for signs of communications module failures or unexpected restarts. Check if the device becomes unreachable remotely.Affected if The communications module exhibits crashes or unexpected behavior
A defender is affected if they have a Medfusion 4000 pump running firmware version 1.1, 1.5, or 1.6 with the communications module enabled on the network.
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 dataIsolate affected pump devices on dedicated network segments to limit exposure, and contact Smiths Medical for available firmware updates or patches addressing this vulnerability. Monitor device availability as the communications module crash could affect remote monitoring capabilities.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12722 — 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-2017-12722 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