dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-9692

MEDIUM · 6.9 CVSS v4.0 Published 2024-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The VIMESA VHF/FM Transmitter Blue Plus contains an unauthenticated denial-of-service vulnerability in the 'doreboot' endpoint. An attacker can send a simple HTTP GET request to this unprotected endpoint to trigger a restart of the transmitter, disrupting broadcast operations without any credentials or authentication.

MitigationImplement authentication and authorization controls on the 'doreboot' endpoint to ensure only authorized personnel can trigger device restarts. Consider network segmentation to limit exposure of management interfaces and add rate limiting to prevent repeated abuse.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the VIMESA transmitter model
    Check the device label, web interface header, or management console for the exact model name and firmware version. The affected product is VIMESA VHF/FM Transmitter Blue Plus.
    Affected if The installed device is a VIMESA VHF/FM Transmitter Blue Plus of any version.
  2. Locate the web management interface
    Access the device's IP address via HTTP in a browser or use curl http://<device-ip>/ to check if a web interface responds.
    Affected if The device exposes a web management interface on the network.
  3. Verify the doreboot endpoint exists
    Send an HTTP GET request to http://<device-ip>/doreboot or http://<device-ip>/cgi-bin/doreboot (common paths for such endpoints). Check if the endpoint responds or triggers a restart.
    Affected if The /doreboot endpoint is reachable and responds to unauthenticated requests.
  4. Confirm no authentication is required
    Attempt to access the doreboot endpoint without providing any credentials, session cookies, or tokens. Observe if the device restarts or returns an error indicating authentication is required.
    Affected if The endpoint accepts the request without any authentication and triggers a device restart.

If you have a VIMESA VHF/FM Transmitter Blue Plus with an accessible web interface and the /doreboot endpoint responds to unauthenticated requests, your environment is affected by CVE-2024-9692.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authentication and authorization controls on the 'doreboot' endpoint to ensure only authorized personnel can trigger device restarts. Consider network segmentation to limit exposure of management interfaces and add rate limiting to prevent repeated abuse.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9692 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data