CVE-2026-85454 in core-moos
Summary
by MITRE • 09/04/2026
MOOS core-moos through 10.4.0 contains a buffer overflow vulnerability in CMOOSSerialPort::GetTelegram() that writes a NUL terminator one byte past the serial telegram stack buffer. Attackers controlling the serial line can send a full-length telegram to trigger the off-by-one write, corrupting the stack and potentially enabling code execution.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 09/04/2026
The MOOS core-moos software suite, specifically through version 10.4.0, contains a critical buffer overflow vulnerability located within the CMOOSSerialPort::GetTelegram() function. This flaw represents an off-by-one error where the implementation writes a NUL terminator one byte past the end of the allocated serial telegram stack buffer. The root cause lies in improper bounds checking during string termination operations, which is a classic memory safety issue often categorized under CWE-193: Off-by-One Error. Such vulnerabilities arise when developers miscalculate array indices or fail to account for null terminators in fixed-size buffers, leading to writes that exceed the intended memory boundaries.
The operational impact of this vulnerability is severe due to its location on the stack and the nature of the data involved. Attackers who have control over the serial line interface can exploit this flaw by sending a telegram with a length equal to the buffer size. This specific input triggers the off-by-one write, causing corruption of adjacent memory locations on the call stack. Stack corruption is particularly dangerous as it can overwrite critical return addresses or saved frame pointers. If an attacker successfully manipulates these overwritten values, they may achieve arbitrary code execution by redirecting program flow to malicious shellcode injected into the process memory. This aligns with ATT&CK technique T1059: Command and Scripting Interpreter if used for initial access or lateral movement within a connected system environment.
From a defensive perspective, this vulnerability highlights the risks associated with low-level serial communication handling in robotics and autonomous systems software like MOOS. The ability to execute code remotely via the serial port significantly expands the attack surface of any device relying on this interface. Mitigation strategies must prioritize immediate patching to version 10.4.1 or later where this issue has been addressed by correcting the buffer boundary checks. In environments where updating is not immediately feasible, network segmentation and strict input validation at the application layer can help mitigate risk. Developers should also adopt secure coding practices that enforce bounds checking for all string operations involving fixed-size buffers to prevent similar off-by-one errors in future iterations of the codebase.