Summary
MOOS core-moos contains a hard-coded passphrase in the SuicidalSleeper component, which uses it to authorize multicast process-control commands. A peer that can reach the configured multicast network may use the known passphrase to enumerate MOOS processes and request their termination, disrupting services.
Affected context
The vulnerability occurs in MOOS deployments using the SuicidalSleeper component with its default multicast group and port. Risk is higher when untrusted or insufficiently isolated hosts can reach the multicast channel and the component relies on the embedded passphrase for command authorization.
Exploit preconditions
- Attack surface: The MOOS multicast command channel
- Required access: Network reachability to the configured multicast group and port
- Trigger point: Processing of an authorized process-termination command
- Why exploitation is possible: The authorization secret is hard-coded and therefore discoverable, allowing reachable peers to issue commands accepted by the component
Why this happens
The underlying flaw is the inclusion of a fixed authentication secret in application logic for authorizing sensitive multicast commands. Because the credential is shared, static, and not independently provisioned per deployment or peer, anyone who can obtain the software and reach the command channel may be able to reuse it. This behavior maps to CWE-798, Use of Hard-coded Credentials.
Potential impact
- An attacker may terminate selected MOOS processes remotely.
- Critical robotics or distributed-control services could be disrupted.
- Repeated termination requests could cause denial of service.
- Unexpected shutdowns could interrupt operations, monitoring, or recovery workflows.
- A compromised multicast-reachable host could affect other trusted peers.
General mitigation guidance
Mitigation generally focuses on removing shared embedded secrets from
authorization decisions and reducing exposure of the multicast control
plane.
Common defensive patterns include:
- Using securely provisioned, rotatable credentials or peer-specific authentication.
- Requiring authenticated and integrity-protected control messages.
- Restricting multicast membership and filtering traffic at network boundaries.
- Separating control traffic from untrusted or broadly reachable networks.
- Applying least privilege to MOOS processes and limiting which components can terminate peers.
- Using fail-safe authorization and explicit allowlists for sensitive process-control operations.
- Avoiding default credentials and treating configuration secrets as deployment-managed values.
How teams detect issues like this
Organizations can look for this vulnerability through:
- Static analysis searches for hard-coded passwords, passphrases, or authentication tokens.
- Code review checks covering multicast command handlers and process-control authorization.
- Dependency and source audits for embedded default credentials in distributed components.
- Network monitoring for unexpected multicast process-enumeration or termination commands.
- Policy enforcement that blocks sensitive control protocols from untrusted network segments.
- Automated security review tools that flag credential literals and unauthenticated administrative commands.

