Skip to main content
VulnerabilityPublished Updated

CVE-2024-36981: OpenPLC_v3 · Out-of-bounds Read

Affects OpenPLC_v3Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Monitor OpenPLC vendor channels and security advisories closely for official patches or updates addressing CVE-2024-36981 and apply them promptly once available.
  2. Implement network segmentation to isolate OpenPLC devices from general IT networks and restrict access to EtherNet/IP services only to trusted management systems.
  3. Deploy firewall rules and intrusion detection/prevention systems (IDS/IPS) to detect and block malformed or suspicious EtherNet/IP PCCC requests that could exploit the vulnerability.
  4. Conduct regular network traffic analysis to identify anomalous patterns indicative of exploitation attempts targeting the OpenPLC runtime.
  5. Limit exposure by disabling unused network services and protocols on OpenPLC devices to reduce the attack surface.
  6. Employ strict access controls and monitoring on networks hosting industrial control systems to prevent unauthorized lateral movement.
  7. Prepare incident response plans specific to industrial control system outages to minimize downtime and ensure rapid recovery.
  8. Consider deploying virtual patching or application-layer gateways that can filter malicious EtherNet/IP traffic until official patches are applied. These measures go beyond generic advice by focusing on network-level controls and operational preparedness tailored to the industrial environment.

Description

An out-of-bounds read vulnerability exists in the OpenPLC Runtime EtherNet/IP PCCC parser functionality of OpenPLC_v3 b4702061dc14d1024856f71b4543298d77007b88. A specially crafted network request can lead to denial of service. An attacker can send a series of EtherNet/IP requests to trigger this vulnerability.This is the final instance of the incorrect comparison.

References

Community reviews

Loading reviews…