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 arbitrary variable notifications without validation.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/moos-ivp/moos-ivp/commit/3907ac07cdfd8a7255d65657dc18dc6b77b30b64 Patch
- https://github.com/moos-ivp/moos-ivp/pull/122 Issue Tracking, Patch, Exploit
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.7 · mitNVD modified 2026-10-14 15:16
Affected (CPE criteria) 1
cpe:2.3:a:mit:moos-ivp:*:*:*:*:*:*:*:*
References 5
- https://github.com/moos-ivp/moos-ivp Product
- https://github.com/moos-ivp/moos-ivp/blob/1de9ae146cd63c209e8c3fd81611a4ed2472971b/ivp/src/uFldNodeComms/FldNodeComms.cpp#L114 Product
- https://github.com/moos-ivp/moos-ivp/commit/3907ac07cdfd8a7255d65657dc18dc6b77b30b64 Patch
- https://github.com/moos-ivp/moos-ivp/pull/122 Issue Tracking, Patch, Exploit
- https://www.vulncheck.com/advisories/moos-ivp-through-24.8.1-ufldnodecomms-node-message-source-spoofing Third Party Advisory, VDB Entry