Moquette
Moquette fails open when configured authentication or authorization classes cannot load
Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, when a configured authenticator or authorizator class cannot be loaded, Server.initializeAuthenticator and Server.initializeAuthorizatorPolicy treat the failure as though no custom class was configured and fall back to AcceptAllAuthenticator or PermitAllAuthorizatorPolicy. A misspelled class name, missing dependency, constructor failure, or classpath problem can therefore start the broker with authentication or authorization disabled even though the operator configured those controls. 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/967
- Patch github.com/moquette-io/moquette/commit/14a2f4f…
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.