SCRAM: Silent channel-binding authentication downgrade via unsupported certificate algorithms
ongres scram
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| com.ongres.scram:scram-client Maven |
|
|
| com.ongres.scram:scram-common Maven |
|
|
ongres scram
| Product | Affected | Fixed in |
|---|---|---|
| com.ongres.scram:scram-client Maven |
|
|
| com.ongres.scram:scram-common Maven |
|
|
SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to 3.3, a flaw in com.ongres.scram:scram-client and com.ongres.scram:scram-common allows an attacker capable of a TLS man-in-the-middle attack to silently downgrade a connection from SCRAM-SHA-256-PLUS with channel binding to standard SCRAM-SHA-256 without channel binding when TlsServerEndpoint processes an X.509 certificate using a modern signature algorithm such as Ed25519; getChannelBindingData() can return an empty byte array after NoSuchAlgorithmException, and the ScramClient builder treats that as absent channel-binding data. This issue is fixed in version 3.3.
From the CVE record · GitHub_M
Before version 3.3, scram-client and scram-common can treat channel-binding data as absent when TlsServerEndpoint processes an X.509 certificate using a modern signature algorithm such as Ed25519. An attacker capable of a TLS man-in-the-middle attack can then silently downgrade a connection from SCRAM-SHA-256-PLUS to SCRAM-SHA-256 without channel binding.
Teams using Maven packages com.ongres.scram:scram-client or com.ongres.scram:scram-common at versions earlier than 3.3 should check their dependencies.