# CVE-2024-23766: Denial of service in n/a

> Unauthenticated attackers can cause denial of service on HMS Anybus X-Gateway devices by sending repeated GET requests to a specific URL.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-4cqv-cv9m-26q8

## What is CVE-2024-23766?

CVE-2024-23766 is a high-severity denial of service vulnerability in n/a, published on 26 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on HMS Anybus X-Gateway AB7832-F 3 devices. The gateway exposes a web interface on port 80. An unauthenticated GET request to a specific URL triggers the reboot of the Anybus gateway (or at least most of its modules). An attacker can use this feature to carry out a denial of service attack by continuously sending GET requests to that URL.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

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


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

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

## Is CVE-2024-23766 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23766 is a high-severity denial of service vulnerability in n/a, published on 26 Jun 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-23766 in the wild and no public exploit code.

Affected product: n/a. 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-23766/ (Markdown: https://insights.sbomify.com/CVE-2024-23766/index.md)
```

## Sources

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

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