MOOS core-moos through 10.4.0 fails to validate client identity in MOOSDB message processing, allowing authenticated attackers to attribute writes to other clients by supplying arbitrary source identifiers in serialized messages. Attackers can forge message origins and cancel third-party subscriptions by exploiting the disconnect between authenticated connection identity and wire-supplied source attribution.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/themoos/core-moos/commit/26308f0e393f0e80bfa09b275891e776b8dbf522 Issue Tracking, Patch
- https://github.com/themoos/core-moos/pull/76 Issue Tracking, Patch
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.8 · themoosNVD modified 2026-10-14 14:43
Affected (CPE criteria) 1
cpe:2.3:a:themoos:core-moos:*:*:*:*:*:*:*:*
References 5
- https://github.com/themoos/core-moos Product
- https://github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/DB/MOOSDB.cpp#L748 Issue Tracking
- https://github.com/themoos/core-moos/commit/26308f0e393f0e80bfa09b275891e776b8dbf522 Issue Tracking, Patch
- https://github.com/themoos/core-moos/pull/76 Issue Tracking, Patch
- https://www.vulncheck.com/advisories/moos-core-moos-through-10.4.0-moosdb-message-source-spoofing-via-wire-identity Third Party Advisory