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.
Affected products
opener_project: opener
References3
- github.com/EIPStackGroup/OpENer/issues/563 ExploitIssue TrackingVendor Advisory
- github.com/EIPStackGroup/OpENer/issues/563 ExploitIssue TrackingVendor Advisory
- gist.github.com/MrAlaskan/e160c626a32e03e5d9eddaa732560672 Third Party Advisory
Metrics
- CVSS 3.1
-
9.1
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H - EPSS — exploit probability
- 1% percentile: 51 · as of 15 November 2026
- CWE
- CWE-190
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.