# CVE-2024-3742: Electrolink FM/DAB/TV Transmitter Cleartext Storage of Sensitive Information

> Attackers can access system credentials stored in clear text on Electrolink broadcast transmitters, leading to unauthorized access.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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-q9cj-qf3m-4wrv

## What is CVE-2024-3742?

CVE-2024-3742 is a high-severity 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

Electrolink transmitters store credentials in clear-text. Use of these credentials could allow an attacker to access the system.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2024-3742 being exploited?

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

Public exploit code:

- Electrolink FM/DAB/TV Transmitter (controlloLogin.js) - Credentials Disclosure (nuclei): http/cves/2024/CVE-2024-3742.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3742 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3742 exists.

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

## Sources

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

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