How to fix: Certificate requires OCSP stapling but none was stapled
The certificate carries the RFC 7633 TLS Feature extension requesting status_request. That is OCSP Must-Staple, and the handshake returned no stapled OCSP response.
Why it matters
A client that enforces must-staple treats a handshake with no stapled response as a hard failure and refuses to connect. That is a self-inflicted outage, and it appears intermittently rather than at deploy time, because a server normally stops stapling when its own OCSP fetch starts failing.
Must-staple is a promise the certificate makes on the server's behalf: every handshake will carry a fresh, CA-signed revocation status. It is a strong control, since it closes the soft-fail gap that makes revocation largely ineffective, but it only works if stapling is configured, working, and monitored. A certificate that declares it against a server that does not staple is the worst combination of the two.
How to fix it
- 1Enable OCSP stapling on the TLS terminator: ssl_stapling on plus ssl_stapling_verify on in Nginx, SSLUseStapling On in Apache.
- 2Make sure the server can reach the CA's OCSP responder outbound and has a working resolver configured; a blocked responder is the usual cause of stapling stopping silently.
- 3Monitor for a stapled response continuously in production, not only at deploy time.
- 4If stapling cannot be made reliable, reissue without the must-staple extension rather than leaving the promise unmet.
Code examples
Nginx: enable and verify stapling
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/ssl/certs/chain.pem;
resolver 1.1.1.1 8.8.8.8 valid=300s;
resolver_timeout 5s;Confirm a response is actually stapled
openssl s_client -connect example.com:443 -status </dev/null 2>&1 \
| grep -A2 "OCSP Response Status"References
Detected automatically by VulnRadar. The check id is tls-must-staple-not-stapled, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is Certificate requires OCSP stapling but none was stapled?
- VulnRadar rates this high 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-must-staple-not-stapled, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Certificate requires OCSP stapling but none was stapled map to?
- It maps to CWE-299. 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.