Selection of Less-Secure Algorithm During Negotiation
CWE-757
A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used in a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.
We track 19 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.2.
Latest Selection of Less-Secure Algorithm During Negotiation vulnerabilities
- 8.8 High severity
async-http-client: Incorrect Implementation of Authentication Algorithm
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. In 3.0.12, a peer offering only Digest qop=auth-int causes mutual-authentication verification to be skipped. AuthenticatorUtil
- 8.7 High severity
async-http-client: Cleartext Transmission of Sensitive Information
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Prior to 3.0.13 and 2.16.1, Realm.Builder treats a Digest challenge that yields no usable nonce as a Basic challenge. A malici
- 9.2 Critical severity
Apache PLC4X: Improper Certificate Validation
Improper Verification of Cryptographic Signature and Improper Certificate Validation in the OPC UA driver of Apache PLC4X (PLC4J) allows an attacker in a network position between client and server to impersonate the OPC UA server and to read, forge or modify s
- 8.8 High severity
WeenyGenius: Selection of Less-Secure Algorithm During Negotiation
WeenyGenius, a computer lab management system by Howyar Technologies, has a Use of Insecure Protocol vulnerability. Due to the reliance on ZMTP Null mode, unauthenticated attackers on the same network can capture packets to leak transmitted data, or perform re
- 8.8 High severity
MongoDB Server: Selection of Less-Secure Algorithm During Negotiation
An issue in MongoDB Server's intra-cluster connection setup could allow a party with suitable network access to influence which authentication mechanism is used when one replica set member connects to another. Under certain conditions, this could cause the clu
- 7.4 High severity
OTP: Selection of Less-Secure Algorithm During Negotiation
The Erlang/OTP ssl TLS 1.2 (and earlier) and DTLS client does not verify that the cipher suite selected by the server in ServerHello was among the suites offered by the client in ClientHello. The client-side tls_handshake:hello/5 handler validates the negotiat
- 7.5 High severity
i: Selection of Less-Secure Algorithm During Negotiation
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to send a specifically crafted message and downgrade the Transport Layer Security (TLS) protocol to a version disabled in the server configuration.
- 8.2 High severity
scram: Not Failing Securely
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 all
- 7.5 High severity
Anviz CrossChex Standard: Selection of Less-Secure Algorithm During Negotiation
Anviz CrossChex Standard is vulnerable when an attacker manipulates the TDS7 PreLogin to disable encryption, causing database credentials to be sent in plaintext and enabling unauthorized database access.
- 7.6 High severity
Silicon Labs Z-Wave SDK: Selection of Less-Secure Algorithm During Negotiation
When SmartStart Inclusion fails during the onboarding of a Z-Wave PIR sensor, the sensor will join the network as a non-secure device. This vulnerability exists in Silicon Labs' Z-Wave PIR Sensor Reference design delivered as part of SiSDK v2025.6.0 and v2025.
- 7.5 High severity
NetWorker: Selection of Less-Secure Algorithm During Negotiation
Dell NetWorker, versions 19.12.0.1 and prior, contains a Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Inform
- 8.3 High severity
SIMPLE.ERP: Selection of Less-Secure Algorithm During Negotiation
SIMPLE.ERP client is vulnerable to MS SQL protocol downgrade request from a server side, what could lead to an unencrypted communication vulnerable to data interception and modification. This issue affect SIMPLE.ERP from 6.20 to 6.30. Only the 6.30 version rec
- 9.1 Critical severity
iOS and iPadOS: Out-of-bounds Write
An out-of-bounds write was addressed with improved input validation. This issue is fixed in iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, visionOS 2.3. An attacker may be able to cause unexpected system termination or
- 9.1 Critical severity
Wapro ERP Desktop: Selection of Less-Secure Algorithm During Negotiation
Wapro ERP Desktop is vulnerable to MS SQL protocol downgrade request from a server side, what could lead to an unencrypted communication vulnerable to data interception and modification. This issue affects Wapro ERP Desktop versions before 9.00.0.
- 9.1 Critical severity
caterease: Selection of Less-Secure Algorithm During Negotiation
An issue in Horizon Business Services Inc. Caterease 16.0.1.1663 through 24.0.1.2405 and possibly later versions, allows a remote attacker to perform a Drop Encryption Level attack due to the selection of a less-secure algorithm during negotiation.
- 7.5 High severity
dex: Inadequate Encryption Strength
Dex is an identity service that uses OpenID Connect to drive authentication for other apps. Dex 2.37.0 serves HTTPS with insecure TLS 1.0 and TLS 1.1. `cmd/dex/serve.go` line 425 seemingly sets TLS 1.2 as minimum version, but the whole `tlsConfig` is ignored a
- 7.5 High severity
Security Directory Suite: Use of a Broken or Risky Cryptographic Algorithm
IBM Security Directory Suite 8.0.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 228568.
- 8.1 High severity
Red Hat build of Quarkus 2.13.8.Final: Selection of Less-Secure Algorithm During Negotiation
A vulnerability was found in quarkus-core. This vulnerability occurs because the TLS protocol configured with quarkus.http.ssl.protocols is not enforced, and the client can force the selection of the weaker supported TLS protocol.
- 7.8 High severity
My Cloud: Selection of Less-Secure Algorithm During Negotiation
The Western Digital My Cloud Web App [https://os5.mycloud.com/] uses a weak SSLContext when attempting to configure port forwarding rules. This was enabled to maintain compatibility with old or outdated home routers. By using an "SSL" context instead of "TLS"