How to fix: Self-Signed Certificate in Production
The TLS certificate is self-signed (issuer equals subject with no trusted CA chain). Browsers display a hard error and require users to manually bypass the warning.
Why it matters
Users who bypass the self-signed certificate warning receive no guarantee of server identity. Attackers can present any self-signed certificate during a MITM attack and users are trained to click through the warning.
Self-signed certificates are appropriate for development environments but must never be used in production. They provide encryption but no authentication, which defeats half the purpose of TLS.
How to fix it
- 1Replace with a certificate from a publicly trusted CA.
- 2Let's Encrypt provides free certificates with 90-day lifetime and auto-renewal via certbot or ACME clients.
Code examples
Let's Encrypt via certbot
certbot --nginx -d example.com -d www.example.com
# Auto-renewal
certbot renew --dry-runReferences
Detected automatically by VulnRadar. The check id is tls-cert-self-signed, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is Self-Signed Certificate in Production?
- 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-cert-self-signed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Self-Signed Certificate in Production 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.