CVE-2026-129802 in SOESinfo

Summary

by MITRE • 11/21/2026

EOE_set_ip reads each network parameter field (MAC, IP, subnet, gateway, DNS IP, DNS name) from the mailbox payload before checking whether the payload is large enough to contain them. The single bounds check at the end of the function does not prevent the reads from happening. A master can send a Set-IP frame with all flags set and mbxheader.length equal to the minimum, causing all reads to access memory past the end of the payload.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in the EOE_set_ip function represents a critical out-of-bounds read condition stemming from improper input validation sequencing within network parameter processing logic. The core technical flaw lies in the order of operations performed by the software when handling incoming Set-IP frames. Specifically, the implementation attempts to extract multiple distinct network configuration fields—including MAC address, IP address, subnet mask, gateway, DNS IP, and DNS name—from a mailbox payload before verifying that the payload contains sufficient data to support these extractions. This design error means that memory access operations are executed unconditionally based on assumed payload sizes rather than validated actual lengths. The single bounds check located at the end of the function fails to serve as an effective safeguard because it occurs after the destructive read operations have already taken place, rendering the validation step irrelevant for preventing data leakage or corruption during the extraction phase.

From a technical perspective, this flaw allows a malicious actor acting as a master device in the communication topology to exploit the lack of early boundary verification. By constructing and transmitting a Set-IP frame with all configuration flags enabled while simultaneously setting the mbxheader.length field to its minimum valid value, an attacker can trigger reads that extend beyond the allocated memory buffer associated with the payload. This results in accessing memory locations that are not part of the intended data structure, potentially exposing sensitive information stored in adjacent memory regions or causing undefined behavior depending on how the operating system and hardware handle such illegal access attempts. The severity is compounded by the fact that multiple fields are read sequentially, increasing the volume of unauthorized memory accesses per single exploit attempt.

The operational impact of this vulnerability extends beyond simple data leakage. Depending on the specific architecture and security mitigations in place, reading past the end of a buffer can lead to information disclosure where internal system states or other process data become visible through side channels or error messages. In more severe scenarios, particularly if subsequent code relies on these corrupted values for further processing, it could contribute to logic errors that might be leveraged for denial-of-service conditions by causing crashes or instability in the network stack. Furthermore, such out-of-bounds reads are often precursors to more complex attacks where an attacker maps memory layouts to bypass address space layout randomization protections, thereby facilitating subsequent exploitation attempts like buffer overflows or arbitrary code execution if write vulnerabilities exist elsewhere in the system.

This vulnerability aligns with Common Weakness Enumeration (CWE) category CWE-125, which describes Out-of-bounds Read, as it involves reading data beyond the intended boundary of a memory buffer. It also relates to CWE-20, Improper Input Validation, due to the failure to validate input size before processing. In terms of offensive security frameworks, this flaw can be categorized under MITRE ATT&CK technique T1537, which covers Transfer Data to Cloud Account via Network Share or similar mechanisms where data exfiltration is a primary goal, although in embedded contexts it may more directly relate to reconnaissance activities aimed at gathering system information. The exploitation vector typically requires network access and the ability to send crafted frames, placing it within remote attack scenarios if the affected device exposes such interfaces externally.

To mitigate this vulnerability, developers must enforce strict input validation prior to any data extraction operations. This involves checking the mbxheader.length field against the cumulative size required for all requested fields immediately upon receipt of the Set-IP frame and rejecting or truncating payloads that do not meet the minimum length requirements before attempting to parse individual parameters like MAC addresses or DNS names. Implementing defensive programming practices such as using safe string handling functions with explicit length limits can further reduce risk. Additionally, enabling compiler-based security features like stack protectors and address sanitizer during development phases helps in detecting such issues early. Regular code audits focusing on the sequence of validation versus processing steps are essential to prevent similar logic errors in other network protocol handlers within the system.

Responsible

Rt-labs

Reservation

11/16/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!