rabbitmq-server: RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
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.
Text from CVE List
Affected versions 4
- rabbitmq-serveraffected: >= 3.13.0, < 3.13.15CVE List
- rabbitmq-serveraffected: >= 4.0.0, < 4.0.20CVE List
- rabbitmq-serveraffected: >= 4.1.0, < 4.1.11CVE List
- rabbitmq-serveraffected: >= 4.2.0, < 4.2.6CVE List