CVE-2017-12725
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 · uneditedA Use of Hard-coded Credentials issue was discovered in Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump, Version 1.1, 1.5, and 1.6. The pump with default network configuration uses hard-coded credentials to automatically establish a wireless network connection. The pump will establish a wireless network connection even if the pump is Ethernet connected and active; however, if the wireless association is established and the Ethernet cable is attached, the pump does not attach the network stack to the wireless network. In this scenario, all network traffic is instead directed over the wired Ethernet connection.
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 Medfusion 4000 Wireless Syringe Infusion Pump versions 1.1, 1.5, and 1.6 contain hard-coded credentials in the default network configuration that enable automatic wireless network association. This allows any device with knowledge of these credentials to connect to the pump's wireless network, potentially enabling unauthorized network access to the medical 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= 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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.
-
Identify the device modelLocate the physical device or its management interface and confirm it is a Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump. Check the device label, serial number, or management console for the model name.Affected if The device is not a Medfusion 4000 pump, then it is not affected.
-
Check the firmware versionAccess the device's system information or about screen via its clinical interface or management software. Look for a firmware or software version field.Affected if The installed version is exactly 1.1, 1.5, or 1.6, then it falls within the affected version range.
-
Verify wireless network capability is enabledAccess the device's network settings or wireless configuration menu. Check if the wireless network feature is turned on or if the device has any wireless profiles configured.Affected if Wireless networking is disabled and no wireless profiles exist, the hard-coded credentials cannot be exploited for network association.
-
Inspect wireless network configuration for stored credentialsExamine the device's wireless network settings for any configured SSIDs, saved wireless profiles, or auto-connection settings that use default or pre-configured credentials.Affected if The device has wireless profiles with pre-configured or default credentials stored, indicating the hard-coded credentials are in use.
If the device is a Medfusion 4000 pump with firmware version 1.1, 1.5, or 1.6 and wireless networking is enabled with stored network credentials, it is affected by the hard-coded credential vulnerability.
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 dataContact Smiths Medical for firmware updates that address the hard-coded credentials vulnerability; in the interim, network segment the device and monitor for unauthorized wireless associations.
- Consultation12.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,632.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12725 — 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-12725 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