CVE-2026-51536: n/a
In OpENer 2.3.0 (commit 76b95cf) when parsing incoming CIP (Common Industrial Protocol) network packets, the length parameter is inconsistently typed across the call stack. Specifically, an upstream length calculated as an int is passed to a downstream function that expects an EipInt16 (a 16-bit signed integer). If a maliciously crafted packet with specific length fields is processed, the length parameter can overflow or be truncated into a negative value. This negative length bypasses subsequent bounds checking (due to signed/unsigned comparison issues) and is ultimately used in memory operations, leading to a Stack Buffer Overflow when reading data in DecodePaddedEPath.
AI Analysis
Technical Summary
In OpENer version 2.3.0 (commit 76b95cf), the handling of the length parameter in CIP packet parsing is inconsistent: an upstream int length is passed to a downstream function expecting an EipInt16 (16-bit signed integer). A specially crafted packet can cause this length to overflow or truncate to a negative value, which bypasses bounds checks due to signed/unsigned comparison issues. This leads to a stack buffer overflow during memory reads in the DecodePaddedEPath function, posing a risk of memory corruption.
Potential Impact
The vulnerability allows a crafted CIP network packet to trigger a stack buffer overflow in OpENer 2.3.0. This can lead to memory corruption, potentially causing application crashes or enabling an attacker to execute arbitrary code within the affected process context. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid processing untrusted CIP packets with OpENer 2.3.0. Monitor vendor channels for updates and apply patches promptly once released.
CVE-2026-51536: n/a
Description
In OpENer 2.3.0 (commit 76b95cf) when parsing incoming CIP (Common Industrial Protocol) network packets, the length parameter is inconsistently typed across the call stack. Specifically, an upstream length calculated as an int is passed to a downstream function that expects an EipInt16 (a 16-bit signed integer). If a maliciously crafted packet with specific length fields is processed, the length parameter can overflow or be truncated into a negative value. This negative length bypasses subsequent bounds checking (due to signed/unsigned comparison issues) and is ultimately used in memory operations, leading to a Stack Buffer Overflow when reading data in DecodePaddedEPath.
CVSS v3.1
Score 9.1critical
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In OpENer version 2.3.0 (commit 76b95cf), the handling of the length parameter in CIP packet parsing is inconsistent: an upstream int length is passed to a downstream function expecting an EipInt16 (16-bit signed integer). A specially crafted packet can cause this length to overflow or truncate to a negative value, which bypasses bounds checks due to signed/unsigned comparison issues. This leads to a stack buffer overflow during memory reads in the DecodePaddedEPath function, posing a risk of memory corruption.
Potential Impact
The vulnerability allows a crafted CIP network packet to trigger a stack buffer overflow in OpENer 2.3.0. This can lead to memory corruption, potentially causing application crashes or enabling an attacker to execute arbitrary code within the affected process context. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid processing untrusted CIP packets with OpENer 2.3.0. Monitor vendor channels for updates and apply patches promptly once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-06-08T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a555d1568715ace43ecaaec
Added to database: 07/13/2026, 21:48:05 UTC
Last enriched: 07/13/2026, 22:03:50 UTC
Last updated: 08/26/2026, 22:52:11 UTC
Views: 65
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.