Medfusion 4000 Wireless Syringe Infusion PumpOperating system · Smiths Medical

CVE-2017-12724

HIGH · 8.1 CVSS v3.0 Published 2018-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable 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
A 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 FTP server on the pump contains hardcoded credentials, which are not fully initialized. The FTP server is only accessible if the pump is configured to allow FTP connections.

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

The Medfusion 4000 Wireless Syringe Infusion Pump (versions 1.1, 1.5, 1.6) contains an FTP server with hardcoded credentials that are not fully initialized. If the pump is configured to allow FTP connections, an attacker with network access could use these predictable credentials to authenticate to the FTP server.

MitigationDisable the FTP server functionality on the pump if not required for clinical operations. If FTP access is necessary, contact Smiths Medical for a firmware update that addresses the hardcoded credential vulnerability.

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
Medfusion 4000 Wireless Syringe Infusion PumpOperating system
Affected:= 1.1= 1.5= 1.6

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model
    Identify the physical device or network asset as Smiths Medical Medfusion 4000 Wireless Syringe Infusion Pump. Check device labeling, inventory records, or network scanning results for this specific model name.
    Affected if The device is not a Medfusion 4000 pump - different models are not affected by this CVE.
  2. Check firmware version
    Access the pump's administration interface or check system information screens on the device itself. Look for a version indicator labeled as firmware version, software version, or system version.
    Affected if The installed version is 1.1, 1.5, or 1.6 exactly. Versions outside this range (such as 1.2, 1.3, 1.4, or later) are not listed as affected in this CVE.
  3. Verify FTP server status
    Access the pump's configuration or settings menu. Look for an option related to FTP server, remote access, or network services. Determine whether FTP connectivity is enabled or allowed.
    Affected if FTP server functionality is turned on or configured to accept connections. If FTP is disabled entirely, the hardcoded credentials cannot be exploited even on affected versions.
  4. Test FTP service accessibility
    From a system on the same network, attempt to connect to the pump on TCP port 21 using an FTP client. Check if the pump accepts FTP connections or responds to FTP requests.
    Affected if The FTP service is reachable and accepts connection attempts. An unreachable or non-responsive FTP service reduces exploitability.

You are affected if your Medfusion 4000 pump runs version 1.1, 1.5, or 1.6 AND has the FTP server enabled to accept network connections.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the FTP server functionality on the pump if not required for clinical operations. If FTP access is necessary, contact Smiths Medical for a firmware update that addresses the hardcoded credential vulnerability.

Fix this in Medfusion 4000 Wireless Syringe Infusion Pump Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12724 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12724 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