Defibrillator DashboardApplication · Zoll

CVE-2021-27485

HIGH · 7.5 CVSS v3.1 Published 2021-06-16
Fix available
A fix is available. Upgrade to 2.2 or later.
See remediation →
84/100
Remediation priority · High
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
ZOLL Defibrillator Dashboard, v prior to 2.2,The application allows users to store their passwords in a recoverable format, which could allow an attacker to retrieve the credentials from the web browser.

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 store user passwords in a recoverable format within the web browser, allowing attackers to retrieve stored credentials. This typically indicates insecure client-side password storage using mechanisms like localStorage, cookies, or browser-based credential caching that can be accessed through browser developer tools or malicious scripts.

MitigationUpgrade to ZOLL Defibrillator Dashboard version 2.2 or later, which addresses the insecure password storage. If immediate upgrade is not possible, disable any browser-based password saving features and implement proper server-side session management with secure token-based authentication.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 the installed ZOLL Defibrillator Dashboard version
    Locate the version information in the application UI (typically found in Help, About, or Settings), or check any configuration files or registry entries where the application stores version metadata. Compare the found version to the affected range (< 2.2).
    Affected if The installed version is prior to 2.2
  2. Open browser developer tools and inspect localStorage
    While logged into the ZOLL Defibrillator Dashboard, press F12 to open browser developer tools, navigate to the Application tab (Chrome) or Storage tab (Firefox), expand Local Storage, and examine stored key-value pairs for any containing passwords, credentials, or sensitive user data.
    Affected if Passwords or credentials are found stored in localStorage in plaintext or recoverable format
  3. Inspect sessionStorage for stored credentials
    In the same developer tools window, expand Session Storage (or Storage > Session Storage) and examine contents for any password or credential-related keys that may contain user authentication information.
    Affected if Passwords or credentials are found in sessionStorage
  4. Check browser cookies for stored passwords
    In developer tools, navigate to the Cookies section (Application > Cookies in Chrome) and examine cookie values for the application domain. Look for cookies containing password data, authentication tokens stored alongside passwords, or credential-related information.
    Affected if Passwords or credentials are stored in cookies accessible via JavaScript

You are affected if the installed version is prior to 2.2 AND passwords or credentials are present in browser storage mechanisms (localStorage, sessionStorage, or cookies).

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

Upgrade to ZOLL Defibrillator Dashboard version 2.2 or later, which addresses the insecure password storage. If immediate upgrade is not possible, disable any browser-based password saving features and implement proper server-side session management with secure token-based authentication.

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-27485 — 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-27485 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