A critical authentication bypass vulnerability in the MOOS core-moos wire protocol allows unauthenticated remote attackers to gain full administrative control over the database.

The software fails to implement authentication within its wire protocol, enabling any unauthenticated network client to connect and issue sensitive commands. Attackers can bypass protocol string checks to perform unauthorized actions such as publishing data, subscribing to traffic, or executing the DB_CLEAR command to wipe variables and mail queues.

The ability for an unauthenticated attacker to clear the MOOS database poses a severe risk of operational disruption and data loss, particularly in mission-critical robotics environments. Given the CVSS score of 9.8, this vulnerability represents a critical risk where an attacker can gain full control over the database state without any prior authentication, leading to complete loss of system integrity and availability.

Immediate Action: Upgrade to the latest version of themoos core-moos immediately to implement the required authentication mechanisms.

Proactive Monitoring: Review network access logs for unusual connection attempts to the MOOSDB port and monitor for sudden, unexpected clears of database variables or mail queues.

Compensating Controls: Deploy strict network access control lists (ACLs) or a firewall to restrict access to the MOOSDB port to only authorized, trusted IP addresses and subnets.

Public Exploit Available: Unknown

This vulnerability is classified as critical due to the lack of authentication, which provides an attacker with unrestricted access to sensitive database functions. Organizations should prioritize patching this software across all deployments immediately. If immediate patching is not feasible, network-level segmentation must be enforced to isolate the MOOSDB service from untrusted networks until a secure version is deployed.