{"id":31103,"date":"2026-09-30T20:31:26","date_gmt":"2026-09-30T12:31:26","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-102509"},"modified":"2026-09-30T20:31:26","modified_gmt":"2026-09-30T12:31:26","slug":"cve-2026-102509","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-102509","title":{"rendered":"CVE-2026-102509 &#8211; Memory Allocation with Excessive Size Value, Allocation of Resources Without Limits, and U"},"content":{"rendered":"<p>Memory Allocation with Excessive Size Value, Allocation of Resources Without Limits, and Uncontrolled Recursion in the Java implementation of Apache PLC4X (PLC4J) allow a malicious or impersonated device to exhaust the memory or stack of the client application, causing a denial of service.<\/p>\n<p>In the OPC UA driver these defects are reachable before authentication: the offending data is parsed while the secure channel and session are being established, before the server&#8217;s identity has been bound to it. Configuring a trusted server therefore does not prevent exploitation by an attacker who can<br \/>\nimpersonate it.<\/p>\n<p>The individual defects are:<br \/>\n&#8211; Length-prefixed byte strings are allocated at the size claimed on the wire before the length is checked against the data actually received (0.10.0 through 0.13.1).<br \/>\n&#8211; Array fields in generated protocol parsers pre-allocate a list with the element count claimed on the wire, allowing a single count field to trigger a multi-gigabyte allocation. This parser is shared by all PLC4J drivers; the OPC UA driver is the verified pre-authentication path (0.10.0 through 0.13.1).<br \/>\n&#8211; The OPC UA driver accumulates message chunks without enforcing the negotiated maximum chunk count and message size (0.12.0 through 0.13.1).<br \/>\n&#8211; The OPC UA driver pre-allocates collections using element counts received from the server (0.10.0 through 0.13.1).<br \/>\n&#8211; Recursive protocol types are parsed without a nesting-depth limit. The same defect in the Go implementation is covered by  CVE-2026-102510 https:\/\/cveprocess.apache.org\/cve5\/CVE-2026-102510 .<\/p>\n<p>This issue affects Apache PLC4X: from 0.10.0 before 1.0.0.<\/p>\n<p>Users are recommended to upgrade to version 1.0.0, which fixes the issue.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Memory Allocation with Excessive Size Value, Allocation of Resources Without Limits, and Uncontrolled Recursion in the Java implementation of Apache PLC4X (PLC4J) allow a malicious or impersonated dev<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-31103","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/31103","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=31103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=31103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=31103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}