# CVE-2024-22179: Electrolink FM/DAB/TV Transmitter Authentication Bypass by Assumed-Immutable Data

> Unauthenticated attackers can manipulate parameters to blank credentials, gaining admin access and taking over accounts on Electrolink transmitters.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/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-3v49-294p-4c7w

## What is CVE-2024-22179?

CVE-2024-22179 is a high-severity authentication bypass 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

The application is vulnerable to an unauthenticated parameter 
manipulation that allows an attacker to set the credentials to blank 
giving her access to the admin panel. Also vulnerable to account 
takeover and arbitrary password change.

Weakness: CWE-302 (Authentication Bypass by Assumed-Immutable Data)

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


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

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

## Is CVE-2024-22179 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22179 is a high-severity authentication bypass 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-22179 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-22179/ (Markdown: https://insights.sbomify.com/CVE-2024-22179/index.md)
```

## Sources

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

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