Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

rabbitmq/rabbitmq-java-client

              main @ 55af821
            

Fixes

CVEs

HIGH

Peak severity

35.7%

Coverage

Highlights

Auth Bypass: 2 prior fixes. Scrutinize any change in this area.

src/main/java/com/rabbitmq/client/ConnectionFactory.java: most-fixed (7 issues). Treat as high-risk during review.

3 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: Custom DNS record address resolution logic previously stripped or failed to preserve original hostname contexts, preventing downstream TLS implementation from executing proper hostname verification. This allows for potential active interception or MITM.

Insecure TLS (Missing Hostname Verification): When using non-blocking NIO modes, the original hostname was lost before creating the SSLEngine, preventing appropriate identity validation of the remote peer.

Insecure Defaults: Logic inversions and incorrect null-checks on SSL configuration properties (checking the wrong target such as 'sslContext' instead of 'sslContextFactory') historically left AMQPS connections silently unencrypted or reverted them to insecure, non-TLS defaults.