GHSA-2hjf-7455-w946: aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
- Source:
- OSV.dev
- Published:
- Fetched:
- Updated:
- Affects:
- amqtt
https://osv.dev/vulnerability/GHSA-2hjf-7455-w946 ↗
aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation ### Impact `amqtt` is vulnerable to a remote denial of service caused by improper MQTT topic-filter validation combined with catastrophic regular-expression backtracking. A single client can freeze the entire broker by sending one specially crafted `SUBSCRIBE` packet followed by one `PUBLISH` packet. The vulnerability is caused by two defects: 1. `add_subscription()` validates the placement of the single-level wildcard `+` using substring checks for `/+` and `+/`, rather than verifying that each `/`-delimited level containing `+` is exactly `+`. This allows malformed filters such as `"+/" + "+" * 60` to be accepted instead of rejected with return code `0x80`, as required by MQTT-4.7.1-3. 2. `_matches()` converts every `+` character into the greedy regular-expression fragment `[^/]*` and evaluates the resulting expression with `re.fullmatch()`. A filter containing many adjacent `+` characters can cause catastrophic backtracking when matched against a topic that partially matches but ultimately fails. Topic matching runs synchronously inside the broker’s global broadcast loop. When the malicious match is evaluated, it blocks the asyncio event loop and prevents the broker from processing any other work. The issue was reproduced using a single raw MQTT 3.1.1 TCP connection with no third-party client dependencies. Successful exploitation causes: - Existing message delivery to stop - New MQTT connections to receive no `CONNACK` - Keepalive processing to stop - Broadcast processing to stop - The broker to remain unavailable until the process is restarted Under the default configuration, anonymous clients can exploit the vulnerability without credentials. When authentication is enabled, any authenticated client permitted to create arbitrary subscriptions and publish messages may still exploit it. Authentication alone is therefore not a sufficient mitigation. - Ecosystem: `pip` - Package: `amqtt` - Affected versions: `>= 0.11.0, <= 0.11.3` The vulnerable code is present in the `v0.11.0` release commit, `352678c87e50e501a8a5bb91fab73c9400fa046c`, and remained present on the main branch as of `eeb1e254da9a1e8d9cc68ae754fcedac652e8fc0`. Versions before 0.11.0 were not evaluated. This is a denial-of-service vulnerability only. `re.escape()` prevents arbitrary regular-expression injection, and there is no known path to remote code execution. No confidentiality or integrity impact has been identified. Successful exploitation causes a complete loss of availability for the affected broker process. ### Patches The issue has been patched in the `v0.11.4` released version; all users should upgrade. The completed fix: - Validate topic filters one level at a time - Require any level containing `+` to be exactly `+` - As part of comprehensive MQTT topic-filter validation, require `#` to occupy an entire level and appear only as the final level - Replace the regular-expression matcher with deterministic, level-by-level MQTT topic matching Simply changi Affected: PyPI:amqtt Fixed in: 0.11.4 References: https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946 https://nvd.nist.gov/vuln/detail/CVE-2026-104199 https://github.com/Yakifo/amqtt/pull/361 https://github.com/Yakifo/amqtt/commit/e48a8a65027667f936d415db7f01d3ac350104e0 https://github.com/Yakifo/amqtt https://github.com/Yakifo/amqtt/releases/tag/v0.11.4