Incomplete TLS Certificate Chain
The service does not send the intermediate certificates that link its certificate to a trusted root, so some clients cannot validate it and fail or show a warning.
| Severity | Low |
| CVSS 3.1 | 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 2.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-296: Improper Following of a Certificate's Chain of Trust |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle |
| Category | Cryptographic Failures |
Description
A TLS server is expected to send its own certificate followed by the intermediate CA certificates that link it to a trusted root. The service sends an incomplete chain, usually only its own certificate, so a client that does not already hold the missing intermediate cannot build a path to a root it trusts. Related faults are a chain sent in the wrong order and an outdated intermediate left over from a previous certificate.
The fault is easily missed because desktop browsers often hide it: some fetch missing intermediates from the address in the certificate's Authority Information Access extension, and others keep a cache or preloaded list of known intermediates. Many other clients do neither, including command-line tools, programming language libraries, Android apps and API integrations, and these reject the connection, which can break integrations, mobile apps and automated jobs while the service appears to work in a browser.
The security risk is indirect. Users of affected clients may be shown warnings that they learn to accept, and developers and administrators often respond to the errors by disabling certificate verification in their clients, which leaves those clients open to interception by an attacker who can present any certificate.
The issue is shown by testssl.sh, by openssl s_client -showcerts, which lists exactly what the server sends and reports unable to get local issuer certificate, and by online checkers and vulnerability scanners, which report the chain as incomplete. It typically appears after a certificate is renewed or replaced and only the server certificate file is updated.
Remediation
Configure the service to send the complete chain, from its own certificate up to, but not including, the root:
- On IIS and other Windows services, import the intermediate certificates into the local computer's
Intermediate Certification Authoritiesstore so that Windows sends them with the server certificate. - On load balancers and appliances, upload the intermediate certificates as the chain or CA bundle associated with the server certificate.
- Take the intermediates from the CA's current bundle for the new certificate rather than reusing an old file, as CAs change their intermediates.
- Add a check of the chain to the renewal process, and re-enable certificate verification in any client where it was disabled to work around the error.
Confirm the fix with openssl s_client -showcerts from a client without cached intermediates, checking that each certificate is followed by its issuer and that verification succeeds.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.