12 matches found
CVE-2026-85424
MOOS core-moos (through version 10.4.0) has a missing authentication flaw in its wire protocol (MOOSDB). Unauthenticated clients can bypass the compile-time protocol string check, connect with arbitrary client names, and execute privileged operations including publish , subscribe , and DB_CLEAR (...
CVE-2026-85453
MOOS core-moos through 10.4.0 contains a stored cross-site scripting (XSS) vulnerability in the MOOSDB HTTP interface. The root cause is a failure to escape database contents when rendering HTTP pages, allowing any MOOS publisher to inject script payloads via variable values. These payloads execu...
CVE-2026-85451
MOOS core-moos through 10.4.0 is affected by a remote process termination vulnerability in the SuicidalSleeper component. The root cause is a hard-coded passphrase used for multicast command authorization, allowing any multicast-reachable peer to enumerate MOOS processes and send termination comm...
CVE-2026-85428
MOOS core-moos through 10.4.0 contains an authentication bypass in its optional MOOSDB HTTP server . Unauthenticated clients can send HTTP requests with variable names and values to the MOOSDB HTTP server port, allowing them to modify MOOS variables including actuator and override commands withou...
CVE-2026-85440
MOOS core-moos through 10.4.0 contains a pre-authentication heap overflow in the MOOSCommPkt packet-handling code. During the HandShake phase , a remote attacker can declare a negative packet length , which bypasses the signed integer check in InflateTo() and causes a negative size conversion in ...
CVE-2026-85432
MOOS core-moos through 10.4.0, an underwater robotics middleware, contains a message source spoofing flaw in its MOOSDB message processing layer. The root cause is a failure to validate client identity: the system trusts wire-supplied source identifiers in serialized messages rather than the auth...
CVE-2026-85442
MOOS core-moos versions through 10.4.0 fail to validate packet length declarations in CMOOSCommPkt::OnBytesWritten() (source file: Core/libMOOS/Comms/MOOSCommPkt.cpp, line 99). An unauthenticated attacker on the network can send crafted wire packets with large declared lengths, triggering unbound...
CVE-2026-85454
MOOS core-moos through 10.4.0 contains an off-by-one buffer overflow in CMOOSSerialPort::GetTelegram(), where a NUL terminator is written one byte past the serial telegram stack buffer. An attacker with physical access to the serial line can send a full-length telegram to trigger the write, corru...
CVE-2026-85450
MOOS core-moos through version 10.4.0 contains a denial of service vulnerability in its MOOSDB HTTP server component. The root cause is the creation of unbounded connections and threads without limits , allowing an attacker over the network (no authentication required) to open many connections an...
CVE-2026-85455
MOOS core-moos through 10.4.0 contains a buffer over-read in the CMOOSCommPkt component. A crafted four-byte packet sent over a TCP connection to the MOOSDB port triggers an out-of-bounds memory access during deserialization, allowing an unauthenticated attacker to read process memory. The vulner...
CVE-2026-85443
MOOS core-moos through 10.4.0 has a denial of service vulnerability in MOOSCommServer::ListenLoop(). The accept thread performs a blocking receive without timeout during the wire-protocol handshake. An unauthenticated network attacker can open a TCP connection to the MOOSDB port and send no data,...
CVE-2026-85441
MOOS core-moos through 10.4.0 contains a denial-of-service vulnerability in CMOOSMsg::operator>> , which fails to validate that serialized string lengths are non-negative. An unauthenticated attacker can send a crafted message with a negative length value to the MOOSDB port , triggering an ...