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

> An attacker can cause a denial of service on HMS Anybus X-Gateway devices by sending specific requests to port 7412, requiring a device restart to recover.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-8wv3-qwhx-w2cj

## What is CVE-2024-23765?

CVE-2024-23765 is a medium-severity denial of service vulnerability in n/a, published on 26 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on HMS Anybus X-Gateway AB7832-F 3 devices. The gateway exposes an unidentified service on port 7412 on the network. All the network services of the gateway become unresponsive after sending 85 requests to this port. The content and length of the frame does not matter. The device needs to be restarted to resume operations.

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


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

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

## Is CVE-2024-23765 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23765 is a medium-severity denial of service vulnerability in n/a, published on 26 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23765 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-23765/ (Markdown: https://insights.sbomify.com/CVE-2024-23765/index.md)
```

## Sources

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

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