# CVE-2024-5422: Denial of Service

> Attackers can cause denial of service in SEH Computertechnik print servers by exhausting file descriptors via HTTP requests.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-78m4-c73f-766m

## What is CVE-2024-5422?

CVE-2024-5422 is a high-severity denial of service vulnerability in SEH Computertechnik INU-100, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An uncontrolled resource consumption of file descriptors in SEH Computertechnik utnserver Pro, SEH Computertechnik utnserver ProMAX, SEH Computertechnik INU-100 allows DoS via HTTP.This issue affects utnserver Pro, utnserver ProMAX, INU-100 version 20.1.22 and below.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2024-5422 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5422 is a high-severity denial of service vulnerability in SEH Computertechnik INU-100, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5422 in the wild and no public exploit code.

Affected product: SEH Computertechnik INU-100. 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-5422/ (Markdown: https://insights.sbomify.com/CVE-2024-5422/index.md)
```

## Sources

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

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