Summary
A critical authorization flaw in MOOS essential-moos pShare allows any publisher to send PSHARE_CMD messages without adequate permission checks. An attacker who can publish messages on the MOOS bus may reconfigure network routes and listeners, redirecting or duplicating traffic to attacker-controlled destinations.
Affected context
The vulnerability occurs in deployments using the pShare component to manage MOOS message-bus routes and listeners. It becomes risky when untrusted or insufficiently trusted publishers can reach the pShare command channel and the component accepts runtime route or listener changes without verifying authorization.
Exploit preconditions
- Attack surface: The MOOS message bus and pShare command-handling interface
- Required access: Ability to publish messages that reach the pShare component
- Trigger point: Processing of PSHARE_CMD messages containing route or listener configuration requests
- Why exploitation is possible: Command authorization is not sufficiently enforced before runtime network changes are applied
Why this happens
The underlying bug is an authorization failure in the handling of privileged control messages. pShare accepts commands that can modify network listeners and traffic routes without reliably confirming that the publisher is permitted to perform those operations. This maps to CWE-862: Missing Authorization, where access-control checks are absent or insufficient for a protected function.
Potential impact
- An attacker may open listeners on arbitrary addresses
- Bus traffic could be redirected to attacker-controlled destinations
- Messages may be duplicated, intercepted, or selectively observed
- Network topology and runtime communication behavior could be altered
- Downstream systems may process manipulated or unauthorized messages
- The affected environment could experience loss of confidentiality, integrity, or availability
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the pShare command boundary and reducing trust in message publishers.
Common defensive patterns include:
- Require explicit authorization for commands that create listeners or modify routes
- Use secure-by-default configurations that disable runtime reconfiguration unless needed
- Authenticate and restrict publishers permitted to access privileged command channels
- Apply allowlists for listener addresses, destinations, and permitted route changes
- Separate ordinary message publishing from administrative control operations
- Run pShare with only the network and operating-system privileges it requires
- Segment message-bus traffic and restrict access through network policy controls
How teams detect issues like this
Organizations can look for this issue through:
- Static analysis and code review checks for command handlers without authorization gates
- Review of message-bus ACLs and publisher identity enforcement
- Runtime monitoring for unexpected PSHARE_CMD activity or changes to listeners and routes
- Network telemetry that identifies new outbound destinations or duplicated bus traffic
- Policy checks requiring privileged control messages to use authenticated, allowlisted sources
- Automated security review tools that flag externally influenced administrative operations without access checks

