How to fix: ECDSA Key Size Below P-256
The TLS certificate uses an ECDSA key on a curve smaller than P-256 (secp256r1). Curves below P-256 provide less than 128-bit equivalent security and should be avoided in new certificates.
Why it matters
Smaller ECDSA curves provide weaker cryptographic guarantees. While not yet practically broken, they offer a smaller security margin than modern recommendations require.
NIST recommends P-256 (secp256r1) as the minimum ECDSA curve for new certificates. P-256 provides 128-bit equivalent security. Curves below this (e.g., secp192r1) are considered substandard by modern standards.
How to fix it
- 1Reissue the certificate using ECDSA P-256 or P-384.
- 2Inspect the current key: openssl x509 -in cert.pem -noout -text | grep 'Public Key'
Code examples
Generate P-256 ECDSA key
openssl ecparam -genkey -name prime256v1 -out server.key
openssl req -new -key server.key -out server.csr -subj '/CN=example.com'Inspect key curve
openssl x509 -in cert.pem -noout -text | grep -A2 'Public Key Algorithm'References
Detected automatically by VulnRadar. The check id is tls-cert-key-size-ecdsa, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is ECDSA Key Size Below P-256?
- VulnRadar rates this info 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-cert-key-size-ecdsa, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does ECDSA Key Size Below P-256 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.