# CVE-2024-20484: Cisco Enterprise Chat and Email Denial of Service Vulnerability

> Unauthenticated remote attackers can cause a denial of service in Cisco Enterprise Chat and Email by sending crafted MR PIM traffic, requiring manual service restart.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-jvmc-2wg5-j9pw

## What is CVE-2024-20484?

CVE-2024-20484 is a high-severity denial of service vulnerability in Cisco Enterprise Chat and Email, published on 6 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the External Agent Assignment Service (EAAS) feature of Cisco Enterprise Chat and Email (ECE) could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.

This vulnerability is due to insufficient validation of Media Routing Peripheral Interface Manager (MR PIM) traffic that is received by an affected device. An attacker could exploit this vulnerability by sending crafted MR PIM traffic to an affected device. A successful exploit could allow the attacker to trigger a failure on the MR PIM connection between Cisco ECE and Cisco Unified Contact Center Enterprise (CCE), leading to a DoS condition on EAAS that would prevent customers from starting chat, callback, or delayed callback sessions. Note: When the attack traffic stops, the EAAS process must be manually restarted to restore normal operation. To restart the process in the System Console, choose Shared Resources > Services > Unified CCE > EAAS, then click Start.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-20484?

It affects 1 product.


Products: Cisco Enterprise Chat and Email.

## How do I fix CVE-2024-20484?

No fix has been published for CVE-2024-20484 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-20484 being exploited?

There is no known exploitation of CVE-2024-20484 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Enterprise Chat and Email

- [CVE-2025-20139](https://insights.sbomify.com/CVE-2025-20139/): Denial of service in Cisco Enterprise Chat and Email (high 7.5)
- [CVE-2019-1877](https://insights.sbomify.com/CVE-2019-1877/): Cisco Enterprise Chat and Email Attachment Download Vulnerability (medium 6.5)
- [CVE-2025-20310](https://insights.sbomify.com/CVE-2025-20310/): Cisco Enterprise Chat and Email Stored Cross-Site Scripting Vulnerability (medium 6.1)
- [CVE-2022-20631](https://insights.sbomify.com/CVE-2022-20631/): Cisco Enterprise Chat and Email Cross-Site Scripting Vulnerability (medium 6.1)
- [CVE-2022-20632](https://insights.sbomify.com/CVE-2022-20632/): Cisco Enterprise Chat and Email Cross-Site Scripting Vulnerability (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20484 and fix it if it is affected.

What it is: CVE-2024-20484 is a high-severity denial of service vulnerability in Cisco Enterprise Chat and Email, published on 6 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-20484 in the wild and no public exploit code.

Affected product: Cisco Enterprise Chat and Email. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-20484/ (Markdown: https://insights.sbomify.com/CVE-2024-20484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20484
- OSV: https://osv.dev/vulnerability/CVE-2024-20484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-20484/
Summaries are generated and may contain mistakes; the official description above is the record.