dbcve.org
Emergency ResponderApplication · Cisco

CVE-2024-20352

HIGH · 8.8 CVSS v3.1 Published 2024-04-03
Fix available
A fix is available. Upgrade to 12.5 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
A vulnerability in Cisco Emergency Responder could allow an authenticated, remote attacker to conduct a directory traversal attack, which could allow the attacker to perform arbitrary actions on an affected device. This vulnerability is due to insufficient protections for the web UI of an affected system. An attacker could exploit this vulnerability by sending crafted requests to the web UI. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the affected user, such as accessing password or log files or uploading and deleting existing files from the system.

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

A directory traversal vulnerability in Cisco Emergency Responder's web UI allows authenticated attackers to craft malicious requests that escape the intended directory and access, upload, or delete arbitrary files on the system with the privilege level of the compromised user.

MitigationApply the Cisco patch when available; until then, limit web UI access to trusted users only and monitor logs for anomalous directory traversal patterns.

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
Emergency ResponderApplication
Affected:< 12.5(1)su8b= 14= 14su1= 14su2= 14su3= 14su3a

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. Confirm Cisco Emergency Responder is installed
    Identify whether Cisco Emergency Responder is deployed in your environment by checking for the product's web interface, service processes, or documentation of the installation.
    Affected if The product is not present in your environment.
  2. Determine installed version
    Access the Cisco Emergency Responder administrative interface or use system commands to retrieve the exact version number (typically found in the About page, show command output, or admin settings).
    Affected if You cannot retrieve the version for comparison.
  3. Compare version against affected ranges
    Match your installed version against: 12.5(1)su8b and below, or versions 14, 14su1, 14su2, 14su3, 14su3a. If your version matches any of these, it falls within the affected range.
    Affected if The installed version is one of the affected versions listed.
  4. Verify web UI accessibility
    Confirm whether the Cisco Emergency Responder web interface is exposed to network users. Check firewall rules, access control lists, or reverse proxy configurations that govern access to the web UI port.
    Affected if The web UI is accessible from untrusted networks.
  5. Review user accounts and access logs
    Audit authenticated user accounts with access to the web UI and review recent access logs for any suspicious directory traversal patterns in requests.
    Affected if Unexpected accounts exist or logs show anomalous traversal patterns.

Your environment is affected if Cisco Emergency Responder is installed with a version matching the affected ranges and the web UI is accessible to authenticated users.

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

Apply the Cisco patch when available; until then, limit web UI access to trusted users only and monitor logs for anomalous directory traversal patterns.

Recommended fix Moderate confidence

14su3 or later (for 14.x branch); 12.5(1)su8b or later (for 12.5.x branch)

  1. 1. Back up the current Cisco Emergency Responder configuration and data.
  2. 2. Review Cisco Emergency Responder release notes and upgrade documentation for version 14su3 or later.
  3. 3. Plan maintenance window as upgrade will require system downtime.
  4. 4. Download the fixed release (14su3 or later) from Cisco.com software downloads.
  5. 5. Access the Cisco Emergency Responder administration interface.
  6. 6. Navigate to the upgrade/installation section and upload the new software image.
  7. 7. Follow the on-screen prompts to complete the upgrade process.
  8. 8. After upgrade, verify the web UI is accessible and the vulnerability is addressed.
Caveat Upgrade may require downtime; ensure compatibility with existing Cisco infrastructure and review release notes for any behavioral changes

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

Fix this in Emergency Responder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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