dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-50953

HIGH · 7.5 CVSS v3.1 Published 2025-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
An issue in XINJE XL5E-16T V3.7.2a allows attackers to cause a Denial of Service (DoS) via a crafted Modbus message.

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

The XINJE XL5E-16T PLC (version V3.7.2a) can be forced into a denial-of-service condition when it receives a specifically crafted Modbus message. The vulnerability lies in how the device's Modbus implementation handles certain malformed or specially constructed protocol messages, causing the device to become unresponsive or require restart.

MitigationApply vendor-supplied firmware updates when available; prior to patching, implement network segmentation to restrict Modbus access to authorized endpoints only, and monitor for anomalous Modbus traffic patterns.

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
High

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

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 PLC model
    Access the PLC configuration software (XINJE PLC Programming Tool) or check the device label to confirm the exact model number is XL5E-16T
    Affected if The device is not an XINJE XL5E-16T PLC, then this CVE does not apply
  2. Check the firmware version
    Using the XINJE PLC programming software, navigate to the system information or device status section to retrieve the installed firmware version
    Affected if The firmware version is V3.7.2a; versions other than V3.7.2a may have different vulnerability status
  3. Verify Modbus communication is enabled
    Check the PLC configuration or communication settings in the XINJE programming tool to determine if Modbus RTU or Modbus TCP is configured and active
    Affected if Modbus communication is enabled and configured on the device; if disabled, the attack surface may be reduced
  4. Monitor for device responsiveness issues
    Observe or log whether the PLC becomes unresponsive, experiences communication failures, or requires power cycling or restart to recover
    Affected if The device exhibits unexplained unresponsiveness or requires frequent restarts, especially after receiving Modbus traffic

You are affected if you have an XINJE XL5E-16T PLC running firmware V3.7.2a with Modbus communication enabled, and the device shows signs of becoming unresponsive or requiring restart.

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 vendor-supplied firmware updates when available; prior to patching, implement network segmentation to restrict Modbus access to authorized endpoints only, and monitor for anomalous Modbus traffic patterns.

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-2024-50953 — 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-50953 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