An authentication bypass vulnerability in the MOOSDB HTTP server within core-moos versions 10.4.0 and earlier allows unauthenticated attackers to remotely modify critical system variables.

This vulnerability is an authentication bypass (CWE-306) affecting the optional MOOSDB HTTP server component. Because the server fails to perform any authorization or authentication checks, any unauthenticated network actor can submit HTTP requests to modify internal MOOS variables, including actuator commands and system overrides.

Successful exploitation allows an attacker to manipulate the state of mobile robotics systems controlled by the MOOS framework. This poses a significant risk to operational integrity, as an attacker could force unauthorized actions or disable safety overrides, potentially leading to physical damage, system downtime, or loss of control over robotic assets. The CVSS score of 9.8 reflects the high severity of this flaw, as it requires no privileges and permits direct modification of system behavior over the network.

Immediate Action: Discontinue use of the optional MOOSDB HTTP server feature if it is not strictly required for operations. If the service must remain active, ensure that network access is strictly restricted to trusted management segments via firewall rules to prevent unauthenticated remote access.

Proactive Monitoring: Monitor network traffic directed at the MOOSDB HTTP service port for unusual HTTP GET or POST requests containing variable assignment parameters. Review system logs for unexpected changes to actuator variables or system state overrides.

Compensating Controls: Deploy a Web Application Firewall or an application-layer proxy in front of the MOOSDB service to filter incoming requests and block attempts to invoke the variable modification functions without valid credentials.

Public Exploit Available: No

The vulnerability presents a critical risk to systems utilizing the MOOS framework due to the lack of authentication on sensitive control functions. Organizations should prioritize disabling the affected HTTP server functionality immediately, as it provides an unprotected interface to critical system variables. If the service is essential, isolate the host at the network level until a vendor-supplied patch is applied to enforce proper authentication.