postgresql is vulnerable to Authentication Downgrade
59
Medium Risk
pgJDBC's SCRAM authenticator does not fully enforce channelBinding=require. When the bundled scram-client cannot derive a tls-server-end-point channel-binding hash from the server certificate (for example Ed25519, Ed448, or post-quantum signature algorithms), it supplies an empty binding instead of failing. pgJDBC then accepts negotiation to plain SCRAM-SHA-256 even though the connection was configured to require channel binding, silently removing the MITM protection that setting is meant to provide.
You are affected if you are using a version that falls within the vulnerable range and your JDBC connection properties set channelBinding=require. Connections using the default prefer policy, or allow / disable, are not affected because falling back to plain SCRAM is documented behavior for those modes.
postgresql is vulnerable to Authentication Downgrade in versions 42.7.4 - 42.7.11.
Upgrade the org.postgresql:postgresql library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant