Skip to main content
MediumTLSOWASP A02:2021CWE-295

How to fix: TLS Certificate Chain Missing Intermediate Certificate

Async check: opens a TLS connection and inspects the certificate chain the server actually sent (via the peer certificate's issuer-certificate links), independent of whether the connecting client's own trust store happens to already have the missing intermediate cached. Reports when the handshake verified successfully but the server sent only the leaf certificate.

Why it matters

Clients that don't already have the missing intermediate cached and don't fetch it via AIA, including many non-browser HTTP libraries, older mobile OS TLS stacks, and embedded devices, cannot build a trust path to a root and will reject the connection outright.

TLS servers should send their full certificate chain (the leaf plus every intermediate CA up to, but not including, the root) on every handshake. When only the leaf is sent, verification only succeeds for clients that separately already trust or can fetch the missing intermediate.

How to fix it

  1. 1Configure the server to serve the full certificate chain (commonly the CA-provided 'fullchain.pem' or equivalent bundle), not just the leaf certificate.
  2. 2Verify with: openssl s_client -connect example.com:443 -showcerts, and confirm more than one certificate is returned.

Code examples

Inspect the served chain

bash
openssl s_client -connect example.com:443 -showcerts < /dev/null 2>/dev/null | grep -c 'BEGIN CERTIFICATE'

References

Detected automatically by VulnRadar. The check id is tls-cert-chain-incomplete, stable across every scan so you can filter or diff on it.

See every tls check

Questions

How severe is TLS Certificate Chain Missing Intermediate Certificate?
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-cert-chain-incomplete, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does TLS Certificate Chain Missing Intermediate Certificate map to?
It maps to CWE-295. 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 tls certificate chain missing intermediate certificate

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

TLS Certificate Chain Missing Intermediate Certificate | VulnRadar