dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-5422

HIGH · 7.1 CVSS v4.0 Published 2024-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
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.

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

This vulnerability involves uncontrolled consumption of file descriptors in SEH Computertechnik utnserver devices (Pro, ProMAX, INU-100) leading to denial of service via HTTP requests. The issue allows an attacker to exhaust available file descriptors by sending HTTP requests, preventing the device from accepting new connections.

MitigationUpdate the firmware to a version above 20.1.22. As a temporary workaround, implement network-level rate limiting or firewall rules to restrict HTTP requests from untrusted sources.

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
Low
Authentication
X
User interaction
None
Scope
X

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/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 utnserver device model
    Access the device admin interface or check the device label to confirm it is an SEH Computertechnik utnserver Pro, utnserver ProMAX, or INU-100 model
    Affected if The device is one of these three models (utnserver Pro, ProMAX, or INU-100)
  2. Determine the firmware version
    Log into the device web interface or check via SNMP/sysinfo to retrieve the current firmware version number
    Affected if The installed firmware version is below 20.1.22 (versions 20.1.22 and above contain the fix)
  3. Verify HTTP service is accessible
    Confirm the device has its HTTP management interface exposed on the network by attempting to reach the device IP on port 80 or checking the service status in the admin panel
    Affected if HTTP service is enabled and reachable from network segments where untrusted users could send requests
  4. Check for connection acceptance behavior
    Attempt to establish new HTTP connections to the device or observe whether new connections are being refused or timing out
    Affected if The device is unable to accept new HTTP connections or shows signs of resource exhaustion

A user is affected if they have an utnserver Pro, ProMAX, or INU-100 device running firmware version below 20.1.22 with HTTP interface accessible to potential attackers.

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

Update the firmware to a version above 20.1.22. As a temporary workaround, implement network-level rate limiting or firewall rules to restrict HTTP requests from untrusted sources.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5422 — 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-5422 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