Aedes
Aedes has Uncaught Exception and Uncontrolled Resource Consumption
Aedes is an MQTT broker that can run on any stream server. Prior to 1.1.1, the MQTT broker does not bound topic depth or structural complexity before passing topics through `mqemitter` into `qlobber`. A `PUBLISH`, `SUBSCRIBE`, or registered `Will` message containing an excessively deep topic can reach `qlobber._split_words` in `lib/qlobber.js` and trigger an uncaught `too many words` exception. Calls from `handlers/subscribe.js` and the publishing logic are not protected against that exception, so it escapes to the `Node.js event loop` and terminates the entire broker. The `Will` path is independently reachable when a client disconnects ungracefully: it calls `broker.publish` directly and bypasses the `PUBLISH` handler. An attacker must be able to establish an `MQTT session`, authenticated or unauthenticated according to broker configuration. A successful attack disconnects all legitimate clients and prevents reconnection until the broker process restarts. This issue is fixed in version 1.1.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.1.1
Fixed in 1.1.1
Mitigation
Upgrade aedes to 1.1.1 or later.
References
- Vendor advisory github.com/moscajs/aedes/security/advisories/G…
- Patch github.com/moscajs/aedes/commit/b9024faa4cb416…
- Release notes github.com/moscajs/aedes/releases/tag/v1.1.1
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.