Moquette
Moquette client IDs can cause cross-session H2 durable-queue corruption
Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, H2PersistentQueue derives a session's message-map name as queue_ plus the client ID and its metadata-map name as queue_ plus the client ID plus _meta. A durable session whose client ID ends in _meta can therefore make its message map collide with another client's metadata map. The colliding sessions read and write the same H2 MVStore map with incompatible value types, which can corrupt queue head and tail data and cause message loss, misdelivery, failed queue reloads, or exposure of queued content across sessions. This issue is fixed in version 0.18.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.18.1
Fixed in 0.18.1
Mitigation
Upgrade moquette to 0.18.1 or later.
References
- Vendor advisory github.com/moquette-io/moquette/security/advis…
- Patch github.com/moquette-io/moquette/pull/964
- Patch github.com/moquette-io/moquette/commit/72d6c82…
1 more
- Release notes github.com/moquette-io/moquette/releases/tag/v…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.