A vulnerability in MOOS core-moos allows authenticated attackers to perform message source spoofing, leading to unauthorized data manipulation and denial of service for legitimate clients.

This is an authentication bypass by spoofing (CWE-290) occurring within the MOOSDB message processing logic. The application fails to enforce identity checks, allowing an authenticated client to supply arbitrary source identifiers in serialized messages, effectively impersonating other system components.

The ability to forge message origins poses a significant risk to the integrity of mission-critical robotics communications handled by the MOOS middleware. An attacker can manipulate system state by injecting fraudulent data or force a denial of service by canceling legitimate subscriptions of other clients. Given the CVSS score of 8.2, this high-severity flaw can lead to unauthorized control or erratic behavior in automated systems, potentially resulting in operational failure.

Immediate Action: Upgrade to the latest version of core-moos, as the vendor has provided a fix to address the source identity validation in MOOSDB.

Proactive Monitoring: Review MOOSDB access logs for anomalous message traffic or unexpected subscription cancellations that deviate from established operational baselines.

Compensating Controls: Implement strict network segmentation to limit access to the MOOSDB port, ensuring that only trusted clients can establish connections to the middleware.

Public Exploit Available: No

The vulnerability represents a critical failure in the trust architecture of the MOOS environment. Organizations utilizing core-moos in robotic or automation frameworks must prioritize the application of the vendor patch to prevent malicious actors from subverting inter-process communication. Immediate verification of current deployment versions is required to ensure mitigation against this spoofing risk.