CVE-2024-50953

7.5 HIGH

📋 TL;DR

This vulnerability in XINJE XL5E-16T programmable logic controllers allows attackers to send specially crafted Modbus messages that cause a denial of service, disrupting industrial operations. Organizations using these specific PLCs in industrial control systems are affected.

💻 Affected Systems

Products:
  • XINJE XL5E-16T Programmable Logic Controller
Versions: V3.7.2a
Operating Systems: Embedded PLC firmware
Default Config Vulnerable: ⚠️ Yes
Notes: Affects systems with Modbus TCP enabled. Older versions may also be vulnerable but not confirmed.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete disruption of industrial processes controlled by the PLC, potentially causing production downtime, equipment damage, or safety incidents in critical infrastructure.

🟠

Likely Case

Temporary unavailability of the PLC requiring manual restart, causing production delays and operational disruption until service is restored.

🟢

If Mitigated

Minimal impact with proper network segmentation and monitoring allowing quick detection and isolation of malicious traffic.

🌐 Internet-Facing: HIGH if PLCs are directly exposed to internet via Modbus TCP, as attackers can remotely trigger DoS without authentication.
🏢 Internal Only: MEDIUM as attackers would need internal network access, but Modbus protocol lacks authentication making exploitation straightforward once inside.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending crafted Modbus packets to the PLC's Modbus TCP port (typically 502). No authentication needed for Modbus protocol.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: UNKNOWN

Vendor Advisory: NONE

Restart Required: No

Instructions:

Contact XINJE vendor for firmware updates or security patches. No official fix documented in public sources.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate PLCs in separate network segments with firewall rules restricting Modbus access to authorized systems only.

Port Restriction

all

Block external access to Modbus TCP port 502 at network perimeter firewalls.

🧯 If You Can't Patch

  • Implement strict network access controls allowing only trusted IP addresses to communicate with PLCs on Modbus port
  • Deploy industrial intrusion detection systems monitoring for anomalous Modbus traffic patterns

🔍 How to Verify

Check if Vulnerable:

Check PLC firmware version via programming software or HMI interface. Version V3.7.2a indicates vulnerability.

Check Version:

Use XINJE programming software (XDPPro) to read PLC firmware version from device properties.

Verify Fix Applied:

Verify firmware has been updated to version higher than V3.7.2a or test with controlled Modbus traffic simulation.

📡 Detection & Monitoring

Log Indicators:

  • PLC communication errors
  • Unexpected device restarts
  • Modbus exception responses

Network Indicators:

  • Unusual volume of Modbus requests to port 502
  • Malformed Modbus packets
  • Traffic from unauthorized sources to PLC

SIEM Query:

source_ip:external AND dest_port:502 AND (protocol:modbus OR app:modbus) AND bytes > threshold

🔗 References

📤 Share & Export