RabbitMQ rabbitmq-server
RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, When no CA bundle is available, ssl_options/1 falls back to [{verify, verify_none}] with no warning. An attacker in a man-in-the-middle position can forge the JWKS response, which leads the broker to accept arbitrary JWTs. Preconditions include The OAuth2 plugin must be in use with no cacertfile configured and the OS CA bundle empty or unreadable (for example, in a minimal container), and the attacker must hold a network man-in-the-middle position.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.13.0, < 3.13.15
- >= 4.0.0, < 4.0.20
- >= 4.1.0, < 4.1.11
- >= 4.2.0, < 4.2.6
Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6
Mitigation
Upgrade rabbitmq-server to 3.13.15 or 4.0.20 or 4.1.11 or 4.2.6 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.