在 1.0.3 版本之前的 P-Net 中,当 RPC 请求引用未知的接口或对象 UUID 时,系统不会释放为该请求分配的 RPC 会话,也不会为其启动超时机制。通过反复使用不同的活动 UUID 发起请求,可耗尽所有可用会话。一旦会话耗尽,设备将不再响应任何新的 RPC 请求(包括端点映射器查找和连接请求),除非重启设备。远程未认证攻击者可利用此漏洞导致拒绝服务(DoS)。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-111732 | 9.3 CRITICAL | Out-of-bounds write when parsing AR Vendor Block requests |
| CVE-2026-111733 | 8.7 HIGH | NULL pointer dereference on implicit read of AR specific record index |
| CVE-2026-111736 | 8.7 HIGH | NULL pointer dereference on implicit read of user specific record index |
| CVE-2026-111731 | 8.7 HIGH | Infinite loop when reading PDPortDataCheck record of subslot 0 |
| CVE-2026-112200 | 8.7 HIGH | Resource exhaustion from unreleased AR and RPC session on RPC requests with incorrect endi |
| CVE-2026-111730 | 7.2 HIGH | Out-of-bounds write in CheckPeers block parser due to unvalidated peer station name length |
| CVE-2026-111735 | 7.1 HIGH | Integer underflow leads to out-of-bounds read in pf_cpm_c_data_ind() |
| CVE-2026-111734 | 7.1 HIGH | Missing length validation of EtherType, VLAN and FrameID fields in pf_eth_recv() |
| CVE-2026-115795 | 5.3 MEDIUM | Out-of-bounds read of DCP block header in DCP Set and Identify request parsing |
| CVE-2026-115794 | 2.3 LOW | Alarm data length not validated against received frame length |