dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-24317

MEDIUM · 5.3 CVSS v3.0 Published 2025-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Allocation of resources without limits or throttling issue exists in HMI ViewJet C-more series and HMI GC-A2 series, which may allow a remote unauthenticated attacker to cause a denial-of-service (DoS) condition.

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

A resource exhaustion vulnerability exists in HMI ViewJet C-more series and HMI GC-A2 series panels where the web interface or associated services fail to properly limit or throttle resource allocation. A remote unauthenticated attacker can exploit this by sending specially crafted requests that consume excessive memory, CPU, or connection resources, resulting in denial of service.

MitigationApply available vendor firmware updates when released. In the interim, isolate affected HMIs in a restricted network segment, implement firewall rules to limit external access, and monitor for anomalous traffic patterns that may indicate resource exhaustion attempts.

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
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 HMI model and firmware version
    Access the HMI console or use the vendor's management software to retrieve the model number (ViewJet C-more series or GC-A2 series) and current firmware version. This is typically found in System Settings > About or via the device's built-in web server if accessible locally.
    Affected if The device is a ViewJet C-more series or GC-A2 series panel with the web interface or associated services enabled, and the firmware version falls within the affected range (if known) or cannot be verified as patched.
  2. Verify if the web interface is enabled
    Check the HMI configuration settings for web server/web interface status. This is usually located in Network Settings > Web Server or similar. Look for options like 'Enable Web Server', 'Enable HTTP', or 'Web Interface Access'.
    Affected if The web interface or HTTP/HTTPS service is enabled and accessible, making the resource exhaustion vulnerability exploitable.
  3. Confirm network exposure of the web service
    Review network configuration to determine if the HMI web interface is reachable from external networks or untrusted zones. Check firewall rules, VLAN assignments, and access control lists affecting the HMI device.
    Affected if The HMI web interface is exposed to untrusted networks or the internet, allowing remote unauthenticated attackers to send the specially crafted requests described in the CVE.
  4. Inspect resource limit configurations
    Examine the HMI's web server or system settings for any configured limits on connections, memory allocation, or request throttling. Look for options such as 'Max Connections', 'Request Timeout', 'Resource Limits', or 'DoS Protection'.
    Affected if Resource limits are not configured, disabled, or set to values that would not effectively throttle excessive requests, leaving the device vulnerable to exhaustion attacks.
  5. Check for signs of resource exhaustion
    Monitor the HMI device for symptoms such as unusually high CPU usage, memory consumption, or network connection counts. Review system logs, web server logs, or SNMP metrics if available, looking for patterns of excessive requests or service degradation.
    Affected if The device exhibits unexplained high resource usage or connection spikes, which may indicate active exploitation or successful resource exhaustion attempts.

A user is affected if they have a ViewJet C-more or GC-A2 series HMI with the web interface enabled and exposed to network access, where resource limits are not properly configured to throttle excessive requests.

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

Apply available vendor firmware updates when released. In the interim, isolate affected HMIs in a restricted network segment, implement firewall rules to limit external access, and monitor for anomalous traffic patterns that may indicate resource exhaustion attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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