Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
neo4j/neo4j-java-driver
6.x @ 7a3e985
11
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Auth Bypass: 6 prior fixes. Scrutinize any change in this area.
driver/src/main/java/org/neo4j/driver/internal/SecuritySettings.java: most-fixed (3 issues). Treat as high-risk during review.
1 high-severity fix 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: Connections with expired authorization status were previously released back to the pool and reused, allowing subsequent unauthorized queries to bypass credentials validation. Developers must ensure that authorization state transitions actively close and invalidate pooled connections.
Insecure TLS: Insecure handling of high-trust URI schemes failed to enforce hostname verification by default for system CA-signed certificates, exposing client traffic to Man-in-the-Middle (MitM) attacks.
Broken Cryptography: An insecure default configuration allowed 'TrustAllCertificates' and disabled hostname verification. Centralizing secure defaults that reject arbitrary untrusted certs by default is vital to prevent transport degradation.