Impact

Successful exploitation of CVE-2026-85452 allows an attacker to achieve code execution within the context of the user running the ui-moos application. This could result in unauthorized system access, data exfiltration, or total compromise of the affected workstation. Given that MOOS is typically used in robotics, marine, and autonomous systems, the operational impact of such a compromise could involve the loss of control over autonomous vehicles or failure of critical mission software.

Recommendation

Prioritize updating the ui-moos component to a version beyond commit 50b9c6c. Since no official patch release version is specified, verify the fix via source code analysis of the commit history to ensure the sprintf usage has been replaced with safer functions like snprintf. In environments where immediate patching is not possible, implement network segmentation and strict access controls to limit the ability of unauthorized entities to send MOOS identifier packets or interact with the ui-moos process list features.

Attack Chain

1. Attacker establishes network connectivity to the target MOOSDB port.
2. Attacker crafts a malicious MISSION_FILE message containing arbitrary commands within 'Run' entries.
3. Attacker publishes the crafted message to the MOOSDB via the MOOS protocol.
4. The pAntler component receives the malicious MISSION_FILE message from the MOOSDB.
5. pAntler parses the 'Run' entries within the message without validating the input.
6. pAntler calls the execvp() system call, passing the malicious entries.
7. The operating system executes the attacker-defined program on the host.

Impact

Successful exploitation allows unauthenticated remote attackers to execute arbitrary programs on systems running affected versions of essential-moos. This can lead to full system compromise, loss of control over autonomous mission software, and data exfiltration. The vulnerability affects research and robotics environments utilizing the MOOS-IvP middleware.

Recommendation

1. Upgrade the essential-moos software to a version beyond 10.0.1 immediately, if available, or isolate MOOSDB instances from untrusted network segments.
2. Implement network access controls (NAC) to restrict communication with the MOOSDB port to authorized and authenticated mission components only.
3. Audit environments for the use of pAntler and ensure process execution policies are configured to minimize the impact of unauthorized sub-process spawning.

Attack Chain

1. Attacker establishes a TCP/IP connection to the target host on the MOOS communication port.
2. Attacker initiates the HandShake phase of the communication protocol.
3. Attacker crafts a malicious packet header containing a negative integer in the packet length field.
4. The victim application receives the malicious packet via the InflateTo() function.
5. The vulnerability in the signed integer check allows the negative length to pass validation.
6. The application performs a heap-based memory allocation based on the unchecked length.
7. The recv() function processes the attacker-supplied data, resulting in a heap overflow of the internal four-byte buffer.
8. Attacker achieves arbitrary memory write, leading to remote code execution or process termination.

Impact

Successful exploitation of this vulnerability allows unauthenticated remote attackers to execute arbitrary code or cause a denial-of-service condition on affected MOOS installations. This affects systems utilizing MOOS core-moos versions 10.4.0 and earlier. Organizations relying on this software for underwater vehicle communication or similar robotics research environments are at high risk if instances are exposed to untrusted networks.

Recommendation

Prioritized, concrete actions:

• Patch core-moos by upgrading to a version exceeding 10.4.0 immediately upon release of vendor updates.
• Until patching is possible, restrict access to MOOS communication ports via host-based firewalls or network access control lists to known trusted endpoints only.
• Monitor network traffic for anomalous packet headers directed toward MOOS services, specifically looking for TCP streams containing negative length identifiers in the handshake phase.