Defibrillator DashboardApplication · Zoll

CVE-2021-27489

HIGH · 8.8 CVSS v3.1 Published 2021-06-16
Fix available
A fix is available. Upgrade to 2.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
ZOLL Defibrillator Dashboard, v prior to 2.2, The web application allows a non-administrative user to upload a malicious file. This file could allow an attacker to remotely execute arbitrary commands.

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

ZOLL Defibrillator Dashboard versions prior to 2.2 contain an arbitrary file upload vulnerability that allows non-administrative users to upload malicious files to the web application. The lack of proper file validation and authorization checks on the upload functionality permits attackers to upload executable files that can lead to remote command execution.

MitigationUpgrade to version 2.2 or later. If immediate patching is not possible, implement strict file type validation, restrict upload permissions to administrators only, store uploaded files outside the web root, and disable script execution in upload directories.

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
Defibrillator DashboardApplication
Affected:< 2.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify ZOLL Defibrillator Dashboard installation
    Locate the ZOLL Defibrillator Dashboard application on your network. Check for services running on typical web ports (80, 443, 8080) or consult your inventory management system for this software.
    Affected if The application is present in your environment.
  2. Determine the installed version
    Access the application's web interface or check the system where it is installed for version information, typically found in an About page, help menu, or in the application configuration files or registry entries.
    Affected if The discovered version is prior to 2.2 (for example, 2.0, 2.1, or any version number less than 2.2).
  3. Verify upload functionality exists
    Log into the ZOLL Defibrillator Dashboard as a non-administrative user and navigate to any file upload features, such as those for uploading patient data, device configurations, or report attachments.
    Affected if The upload interface is present and accessible to non-administrative accounts.
  4. Inspect uploaded files directory
    Examine the web server's file system for upload directories. Check if uploaded files are stored within the web root and if they retain their original extensions.
    Affected if Uploaded files are stored in a location accessible via the web server and retain executable extensions such as .asp, .aspx, .jsp, .php, or .exe.

You are affected if ZOLL Defibrillator Dashboard version 2.2 or later is not installed and the upload feature is accessible to non-administrative users in your environment.

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 2.2 or later
Fixed in 2.2
Interim mitigation

Upgrade to version 2.2 or later. If immediate patching is not possible, implement strict file type validation, restrict upload permissions to administrators only, store uploaded files outside the web root, and disable script execution in upload directories.

Recommended fix High confidence

ZOLL Defibrillator Dashboard v2.2

  1. Verify current installation version of ZOLL Defibrillator Dashboard
  2. Obtain ZOLL Defibrillator Dashboard v2.2 from official ZOLL or authorized distribution channels
  3. Create a complete backup of the current system configuration and data
  4. Follow ZOLL's official upgrade procedure to deploy version 2.2
  5. Verify the upgrade was successful by checking the new version number
  6. Test that file upload functionality works correctly with proper restrictions

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

Fix this in Defibrillator Dashboard Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27489 — 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-2021-27489 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