dbcve.org
MednetApplication · Hospira

CVE-2014-5401

CRITICAL · 9.8 CVSS v3.0 Published 2019-03-26
Fix available
A fix is available. Upgrade to after 5.8 or later.
See remediation →
100/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
Hospira MedNet software version 5.8 and prior uses vulnerable versions of the JBoss Enterprise Application Platform software that may allow unauthenticated users to execute arbitrary code on the target system. Hospira has developed a new version of the MedNet software, MedNet 6.1. Existing versions of MedNet can be upgraded to MedNet 6.1.

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

Hospira MedNet versions 5.8 and prior contain vulnerable versions of JBoss Enterprise Application Platform that allow unauthenticated remote attackers to execute arbitrary code on the affected system due to known JBoss vulnerabilities.

MitigationUpgrade MedNet to version 6.1 as developed and provided by Hospira/Pfizer to remediate the vulnerable JBoss components.

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
MednetApplication
Affected:<= 5.8

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

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

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

  1. Verify Hospira MedNet is installed
    Check system for MedNet installation - look for MedNet in installed programs (Windows), application directories, or the file system under the MedNet installation path
    Affected if Hospira MedNet software is present on the system
  2. Determine installed MedNet version
    Locate MedNet version information - check program files for version files, or use system inventory tools to query the installed MedNet software version
    Affected if Installed version is 5.8 or any version prior to 5.8
  3. Identify JBoss components bundled with MedNet
    Locate the JBoss application server installation within MedNet directories - typically found under the MedNet installation folder in a subdirectory containing JBoss EAP files
    Affected if JBoss EAP components are bundled with the MedNet installation
  4. Check network exposure of JBoss management interfaces
    Scan network accessible ports on the system for JBoss HTTP invoker ports (typically 8080, 8443, or custom ports) and JMX console endpoints - verify if these management interfaces are reachable from network
    Affected if JBoss HTTP invoker, JMX console, or other management interfaces are exposed to the network without authentication
  5. Inspect JBoss configuration for vulnerable settings
    Examine JBoss configuration files (particularly web.xml and jboss-web.xml) for exposed servlets such as JMXInvokerServlet, HessianServlet, or HTTPInvoker that allow unauthenticated invocation
    Affected if JMXInvokerServlet, Hessian/Burlap servlets, or HTTPInvoker are configured and accessible without authentication

The system is affected if Hospira MedNet version 5.8 or lower is installed AND the bundled JBoss management interfaces are network-accessible, allowing unauthenticated remote code execution.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.8
Interim mitigation

Upgrade MedNet to version 6.1 as developed and provided by Hospira/Pfizer to remediate the vulnerable JBoss components.

Recommended fix High confidence

MedNet 6.1

  1. Verify the current MedNet version by checking the software configuration or system information.
  2. Backup all existing MedNet configurations, databases, and related data according to your organization's backup procedures.
  3. Contact Hospira (now Pfizer) or your authorized MedNet vendor to obtain the MedNet 6.1 upgrade package.
  4. Follow Hospira's official upgrade instructions provided with the MedNet 6.1 release, which typically involve stopping the MedNet service, running the upgrade installer, and configuring the new version.
  5. After upgrading, verify that MedNet 6.1 is running correctly and that all clinical workflows function as expected.
  6. Validate that the JBoss vulnerability is no longer present by confirming the MedNet version shows 6.1 or higher.
Caveat Medical device software upgrades typically require validation and testing to ensure compatibility with connected infusion pumps and clinical workflows; coordinate with Hospira/Pfizer and follow your organization's change management process.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mednet Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing24.0 h
  • Review / QA12.0 h
68.0 hours of engineering $11,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-5401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2014-5401 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