Summary
MOOS core-moos through version 10.4.0 does not authenticate clients connecting through its wire protocol. An unauthenticated client may connect with an arbitrary name and obtain publish, subscribe, and database-clearing privileges, including the ability to reset variables and clear client mail queues.
Affected context
The vulnerability occurs in deployments using the MOOS core-moos wire protocol without an effective runtime authentication boundary. Systems are particularly exposed when the protocol is reachable by untrusted or insufficiently isolated networks, because the compile-time protocol string check does not establish the identity or authorization of connecting clients.
Exploit preconditions
- Attack surface: MOOS wire-protocol listener
- Required access: Network connectivity to a reachable MOOS service; valid authentication is not required
- Trigger point: Client connection followed by privileged publish, subscribe, or database operations
- Why exploitation is possible: The protocol accepts clients without verifying identity or authorization, allowing arbitrary client names and privileged requests
Why this happens
The underlying flaw is missing authentication and authorization at the wire-protocol boundary. Client-supplied connection information is treated as sufficient to establish a trusted session, while the compile-time protocol string check does not prove client identity or limit capabilities. This maps to CWE-306: Missing Authentication for Critical Function, because sensitive operations can be reached without an effective authentication step.
Potential impact
- Unauthorized clients may publish misleading or malicious data
- Attackers could subscribe to information exposed through the MOOS database
- Database variables may be reset or removed
- Client mail queues could be cleared, causing service disruption
- Dependent autonomy, robotics, or monitoring workflows could behave unpredictably
General mitigation guidance
Mitigation generally focuses on adding a strong trust boundary around the MOOS wire protocol and reducing the privileges available to unauthenticated or low-trust clients.
Common defensive patterns include:
- Requiring authenticated client identities before accepting protocol sessions
- Enforcing server-side authorization for publish, subscribe, and database-clear operations
- Restricting protocol exposure to trusted network segments or private interfaces
- Applying network access controls, segmentation, and mutually authenticated transport where supported
- Separating administrative operations from routine client capabilities
- Running related services with least privilege and limiting the impact of database resets
- Treating client names and protocol strings as untrusted metadata rather than proof of identity
How teams detect issues like this
Organizations can assess this risk through:
- Static analysis and code review for connection handlers that accept sessions without identity verification
- Tests confirming that unauthenticated clients cannot publish, subscribe, or invoke destructive database operations
- Network monitoring for unexpected MOOS protocol connections or arbitrary client-name patterns
- Policy checks requiring authentication and authorization for control-plane services
- Review of firewall, segmentation, and service-binding configurations to identify unintended protocol exposure
- Automated security testing that exercises privileged operations from unauthenticated sessions

