UFldShoreBroker (<= 24.8.1) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/ufldshorebroker--24.8.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 03 Sep 2026 23:24:53 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgUnauthenticated Bridge Redirection in MOOS-IvP uFldShoreBrokerhttps://feed.craftedsignal.io/briefs/2026-09-moos-ivp-vulnerability/Thu, 03 Sep 2026 23:24:53 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-moos-ivp-vulnerability/MOOS-IvP uFldShoreBroker through version 24.8.1 is vulnerable to unauthorized route manipulation via forged node ping messages, enabling attackers to redirect data to arbitrary network locations.MOOS-IvP uFldShoreBroker, a component used for coordinating data bridging in autonomous marine vehicle simulations and control systems, contains a critical security vulnerability (CVE-2026-85434). The flaw exists because the software fails to authenticate 'NODE_BROKER_PING' messages before processing them to establish outbound bridge routes. By publishing a crafted 'NODE_BROKER_PING' message containing malicious 'HostRecord' data, an attacker can coerce the broker into redirecting variable traffic to arbitrary attacker-controlled IP addresses. This effectively allows an adversary to intercept, modify, or drop sensitive operational data flowing across the bridge, potentially impacting the mission integrity of connected autonomous nodes. This vulnerability affects all versions of uFldShoreBroker up to and including 24.8.1. Defenders must identify any instances of this software within their network segments and restrict message publication access to authorized nodes only.

Impact

Successful exploitation allows for the redirection of sensitive telemetry and control variables to malicious infrastructure. In maritime autonomous systems, this can lead to operational disruption, loss of communication with remote vessels, or the injection of false navigational or control data, potentially causing physical damage or loss of autonomous assets.

Recommendation

  • Upgrade uFldShoreBroker to a patched version beyond 24.8.1 immediately upon vendor availability.
  • Implement strict network segmentation for systems running MOOS-IvP to limit the exposure of the messaging bus to unauthorized participants.
  • Audit and restrict permissions for publishing 'NODE_BROKER_PING' messages to known, authenticated, and trusted sources within the MOOS-IvP network.
  • Monitor network traffic for unexpected outbound connections from nodes running uFldShoreBroker to unknown or non-standard external destinations.
]]>criticaladvisorydenial-of-servicevulnerabilityrobotics