Expired TLS Certificate
The service presents a TLS certificate whose validity period has ended, so clients reject it or warn their users, who may then learn to ignore certificate warnings.
| Severity | Medium |
| CVSS 3.1 | 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Open in the calculator |
| CVSS 4.0 | 7.4 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-324: Use of a Key Past its Expiration Date |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle |
| Category | Cryptographic Failures |
Description
The certificate presented by the service is past its expiry date (the notAfter field) and is no longer valid. The same applies when an intermediate certificate in the chain has expired, even if the server's own certificate is current. Expiry usually means that renewal was missed: no one was responsible for it, the reminder went to a former member of staff, or a renewed certificate was obtained but not installed on every server, load balancer or appliance that uses it. It is most common on internal services and devices that are not monitored, and on test or forgotten systems.
Clients that check validity, which includes all browsers and most TLS libraries, reject the certificate or show a warning. Where they show a warning, users who meet it regularly learn to accept certificate errors, so an attacker able to intercept their traffic could present a certificate of their own and read or alter the session, including credentials. Clients that enforce validity, such as API integrations, mobile apps and browsers on sites protected by HTTP Strict Transport Security, cannot connect at all, which can cause an outage, and administrators may then disable certificate verification in those clients to restore service, leaving them open to interception afterwards.
The issue is shown by the browser warning, by openssl s_client reporting certificate has expired, by testssl.sh and sslscan, and by vulnerability scanners, which compare the certificate's validity dates with the current date. An expired certificate on a public service also suggests that the owner's certificate inventory and renewal process are incomplete.
Remediation
Renew the certificate and install it, with its full chain, everywhere it is used:
- Obtain a new certificate, preferably for a newly generated key, and install it on every server, load balancer, proxy and appliance that presents the old one, then reload or restart each service and check the certificate actually presented.
- Automate issuance and renewal wherever possible, using the ACME protocol (for example Certbot or the platform's built-in ACME client) for publicly trusted certificates, and certificate auto-enrolment in Active Directory Certificate Services for internal ones. The CA/Browser Forum has agreed to reduce the maximum validity of publicly trusted certificates in stages to 47 days by 2029, which makes manual renewal increasingly impractical.
- Keep an inventory of certificates with an owner for each, and monitor expiry dates centrally, with alerts well ahead of expiry. Certificate Transparency logs can be searched to find publicly trusted certificates issued for the organisation's domains.
- Re-enable certificate verification in any client where it was turned off as a workaround.
Confirm the fix by connecting to the service and checking the new certificate's validity dates and chain.
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.