Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
azure/go-amqp
main @ 2d4ae41
2
Fixes
0
CVEs
HIGH
Peak severity
100.0%
Coverage
Highlights
Information Disclosure: 1 prior fix. Scrutinize any change in this area.
conn.go: most-fixed (1 issue). 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.
Insecure TLS Configuration: When developers provided a custom tls.Config, the library failed to default ServerName to the connection hostname, leading to inactive or broken SNI and hostname verification, exposing connections to Man-in-the-Middle (MitM) attacks.
Information Disclosure: SASL authentication details, including cleartext credentials in the InitialResponse payload, were written to debug logs via string representation formatting, exposing secrets to unauthorized local or log-harvesting actors.