Skip to main content
MediumTLSOWASP A02:2021CWE-326

How to fix: Negotiated cipher suite has no forward secrecy

The handshake settled on a static-RSA key-exchange suite at a protocol version below TLS 1.3. The session key is encrypted directly to the certificate's public key rather than derived from an ephemeral exchange.

Why it matters

Traffic recorded today can be decrypted later by anyone who obtains the private key, through a compromise, a legal demand, or a memory-disclosure bug in the server. Forward secrecy removes that possibility entirely by making each session's key ephemeral and unrecoverable from the certificate.

This reports the suite the server actually chose when offered a normal modern cipher list, not merely one it supports, so it means either the server offered no ephemeral suites or it preferred the static one. TLS 1.3 removes static RSA key exchange from the protocol, which is why this only applies to 1.2 and below.

How to fix it

  1. 1Restrict the server's cipher list to ECDHE and DHE suites so no static-RSA suite can be selected.
  2. 2Enable TLS 1.3, where every defined suite provides forward secrecy.
  3. 3Set server cipher preference on, so the server's ordering decides rather than the client's.

Code examples

Nginx: forward-secret suites only

nginx
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384;

See what gets negotiated

bash
openssl s_client -connect example.com:443 </dev/null 2>&1 \
  | grep -E "^(New|Protocol|Cipher)"

References

Detected automatically by VulnRadar. The check id is tls-cipher-no-forward-secrecy, stable across every scan so you can filter or diff on it.

See every tls check

Questions

How severe is Negotiated cipher suite has no forward secrecy?
VulnRadar rates this medium severity in the tls category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id tls-cipher-no-forward-secrecy, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Negotiated cipher suite has no forward secrecy map to?
It maps to CWE-326. In the OWASP Top 10 it falls under A02:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for negotiated cipher suite has no forward secrecy

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Negotiated cipher suite has no forward secrecy | VulnRadar