# CVE-2024-21846: Electrolink FM/DAB/TV Transmitter Missing Authentication for Critical Function

> Unauthenticated attackers can reset the board and stop transmitter operations via a crafted GET request, causing denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-v8qp-w9p6-9xvp

## What is CVE-2024-21846?

CVE-2024-21846 is a medium-severity missing authorization vulnerability in Electrolink Compact DAB Transmitter, published on 18 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated attacker can reset the board and stop transmitter 
operations by sending a specially-crafted GET request to the command.cgi
 gateway, resulting in a denial-of-service scenario.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2024-21846 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21846 is a medium-severity missing authorization vulnerability in Electrolink Compact DAB Transmitter, published on 18 Apr 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-21846 in the wild and no public exploit code.

Affected product: Electrolink Compact DAB Transmitter. 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-21846/ (Markdown: https://insights.sbomify.com/CVE-2024-21846/index.md)
```

## Sources

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

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