# CVE-2024-9692: Improper Access Control in Input in VIMESA VHF/FM Transmitter Blue Plus

> Unauthenticated attackers can restart the transmitter via an unprotected HTTP endpoint, causing a 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:** 24 Oct 2024
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-hf7q-jwrv-vq2r

## What is CVE-2024-9692?

CVE-2024-9692 is a medium-severity missing authorization vulnerability in VIMESA VHF/FM Transmitter Blue Plus, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VIMESA VHF/FM Transmitter Blue Plus is suffering from a Denial-of-Service (DoS) vulnerability. An unauthenticated attacker can issue an unauthorized HTTP GET request to the unprotected endpoint 'doreboot' and restart the transmitter operations.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-9692 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9692 is a medium-severity missing authorization vulnerability in VIMESA VHF/FM Transmitter Blue Plus, published on 24 Oct 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-9692 in the wild and no public exploit code.

Affected product: VIMESA VHF/FM Transmitter Blue Plus. 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-9692/ (Markdown: https://insights.sbomify.com/CVE-2024-9692/index.md)
```

## Sources

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

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