# CVE-2024-21526: speaker vulnerable to Denial of Service

> Attackers can crash the application by providing unexpected input types to the Speaker object's channels property.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-w5fc-gj3h-26rx

## What is CVE-2024-21526?

CVE-2024-21526 is a high-severity denial of service vulnerability in speaker, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of the package speaker are vulnerable to Denial of Service (DoS) when providing unexpected input types to the channels property of the Speaker object makes it possible to reach an assert macro. Exploiting this vulnerability can lead to a process crash.

Weakness: CWE-241 (Improper Handling of Unexpected Data Type), CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including speaker.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `speaker` | npm | All versions to 0.5.5 | None |
| `speaker` | npm | All versions to 0.5.5 | None |

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

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

## Is CVE-2024-21526 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21526 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21526 is a high-severity denial of service vulnerability in speaker, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21526 exists.

Affected packages and fixed versions:
- speaker (npm): affected all versions up to 0.5.5; no fix listed
- speaker (npm): affected all versions up to 0.5.5; no fix listed

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-21526/ (Markdown: https://insights.sbomify.com/CVE-2024-21526/index.md)
```

## Sources

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

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