Untrusted TLS Certificate
The service presents a certificate that clients cannot trust, such as a self-signed certificate or one from a private authority, so they cannot confirm they reached the genuine server.
| 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-295: Improper Certificate Validation |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle |
| Category | Cryptographic Failures |
Description
The certificate presented by the service does not chain to a certification authority (CA) that clients trust. The usual causes are a self-signed certificate, often generated automatically when software or an appliance is installed; a certificate issued by an internal CA whose root certificate has not been distributed to the clients that connect; or a chain leading to a root that has been removed from trust stores.
Because the certificate cannot be verified, clients have no way to distinguish the genuine service from an impostor presenting a certificate of its own, and an attacker able to intercept traffic, for example on shared Wi-Fi or by ARP or DNS spoofing on an internal network, can present one. Browsers show a full-page warning, and users who reach the service regularly learn to click through it; non-browser clients are often configured to skip certificate verification altogether so that they can connect. A user accustomed to accepting the warning, or a client that does not verify certificates, will then connect through the attacker, who can read and alter everything in the session, including credentials entered at a login page or management interface. The risk is greatest for administrative interfaces and other services that carry credentials or sensitive data.
The issue is shown by the browser warning, by a verification error from openssl s_client, and by testssl.sh, sslscan and vulnerability scanners, which report it under names such as SSL Certificate Cannot Be Trusted or SSL Self-Signed Certificate. A certificate from an internal CA is a problem only for clients that do not trust that CA: where all intended clients are managed devices with the internal root installed, the scanner's result reflects only the tester's own trust store, and this should be checked before the finding is reported.
Remediation
Replace the certificate with one that every intended client trusts:
- For services reached from the internet or by unmanaged devices, use a certificate from a publicly trusted CA. Automated issuance through the ACME protocol, for example with Let's Encrypt and a client such as Certbot, removes most of the cost and effort.
- For internal services, issue the certificate from the organisation's internal CA, such as Active Directory Certificate Services, and distribute the CA's root certificate to all managed clients, for example through Group Policy (
Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies > Trusted Root Certification Authorities) or the device management platform. - Replace the default self-signed certificates on appliances, hypervisors, printers, management controllers and other devices, which are a common source of this finding.
- Configure the server to send the full chain of intermediate certificates.
- Where non-browser clients or scripts were set to skip certificate verification, re-enable it once the certificate is trusted.
For web services, HTTP Strict Transport Security then prevents browsers from offering a way past certificate warnings. Confirm the fix by connecting from a client with a standard trust store, or from a managed device for internal services, and checking that the certificate validates without a warning.
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.