Moos-ivp vulnerabilities
We track 14 vulnerabilities in Moos-ivp products. 14 are rated high or critical, and none are known to be exploited. The most recent was published on September 3, 2026.
Latest Moos-ivp vulnerabilities
- 7.5 High severity
moos-ivp: Allocation of Resources Without Limits or Throttling
MOOS-IvP pMarineViewer through 24.8.1 fails to limit the number of tracked node identities from NODE_REPORT messages, allowing attackers to exhaust memory by supplying unbounded distinct node names. Attackers can publish crafted NODE_REPORT data to cause memor
- 7.5 High severity
moos-ivp: Allocation of Resources Without Limits or Throttling
MOOS-IvP uFldShoreBroker through 24.8.1 fails to limit the number of claimed communities stored in parallel vectors within ShoreBroker::handleMailNodePing(). A single publisher can supply unbounded distinct community names to grow retained state and per-pass w
- 7.5 High severity
moos-ivp: Allocation of Resources Without Limits or Throttling
MOOS-IvP pRealm through version 24.8.1 accepts unbounded REALMCAST_REQ subscriptions without validating duration or variable list limits. Attackers can register long-lived pipeways with many variables to cause pRealm to generate excessive output indefinitely,
- 7.5 High severity
moos-ivp: Inefficient Algorithmic Complexity
MOOS-IvP versions through 24.8.1 contain a quadratic processing vulnerability in uFldNodeComms where each new node identity creates a ledger entry and triggers all-pairs distribution work. Attackers can supply unbounded distinct node names in reports to drive
- 7.5 High severity
moos-ivp: Memory Allocation with Excessive Size Value
MOOS-IvP through 24.8.1 contains a denial of service vulnerability in the Demuxer::addMuxPacket() function that trusts the packet count declared in mux headers without validation. Attackers can declare arbitrarily large packet counts to trigger unbounded memor
- 7.5 High severity
moos-ivp: Out-of-bounds Read
MOOS-IvP through 24.8.1 contains a buffer over-read vulnerability in isQuoted(), isBraced(), and isChevroned() functions that strip whitespace but index using the original string length. Attackers can send NODE_REPORT messages with leading or trailing whitespa
- 7.8 High severity
moos-ivp: Improper Neutralization of Special Elements used in an OS Command
MOOS-IvP through 24.8.1 contains a remote code execution vulnerability in alogsplit's SplitHandler::handlePreCheckSplitDir() function that fails to sanitize shell metacharacters in log file pathnames. Attackers can embed shell syntax in log file names or the -
- 9.8 Critical severity
moos-ivp: Integer Overflow or Wraparound
MOOS-IvP through 24.8.1 contains a buffer overflow vulnerability in StringToIvPFunction() where dimension, piece, and degree counts from encoded BHV_IPF payloads are used as allocation sizes and loop bounds without validation. Attackers can supply crafted payl
- 9.8 Critical severity
moos-ivp: Out-of-bounds Write
MOOS-IvP through 24.8.1 contains multiple buffer overflow vulnerabilities in IvP function string decoders that trust attacker-controlled length fields without validation. Attackers can craft malicious encoded strings with mismatched declared and actual field l
- 9.1 Critical severity
moos-ivp: Insufficient Verification of Data Authenticity
MOOS-IvP uFldNodeBroker through 24.8.1 fails to validate the source of TRY_SHORE_HOST messages on the vehicle bus, allowing any publisher to enroll attacker-controlled shore routes. Attackers can publish malicious shore route messages to receive bridged vehicl
- 9.1 Critical severity
moos-ivp: Insufficient Verification of Data Authenticity
MOOS-IvP uFldShoreBroker through 24.8.1 fails to verify node ping authenticity before creating outbound bridge routes. Attackers can publish NODE_BROKER_PING messages with crafted HostRecord data to redirect bridged variables to attacker-controlled addresses.
- 7.5 High severity
moos-ivp: Insufficient Verification of Data Authenticity
MOOS-IvP uFldNodeComms through 24.8.1 trusts the source node identity from the message body rather than validating it from the connection source. Attackers can craft NODE_MESSAGE packets with spoofed source identities to impersonate other nodes and post arbitr
- 9.8 Critical severity
moos-ivp: Improper Neutralization of Special Elements used in an OS Command
MOOS-IvP uMemWatch through 24.8.1 constructs shell commands from attacker-chosen MOOS client names without sanitization. Attackers can inject shell metacharacters into client names to execute arbitrary commands as the uMemWatch process user through unquoted re
- 9.8 Critical severity
moos-ivp: Improper Neutralization of Special Elements used in an OS Command
MOOS-IvP iSay through 24.8.1 contains a remote code execution vulnerability in the SAY_MOOS variable handler that passes unsanitized text to a shell command. Attackers can publish SAY_MOOS messages containing backticks or command substitution syntax to execute