Skip to content
StrikeOps

Self-Signed, Untrusted or Expired TLS Certificate

LowTypical severity Network and infrastructureCWE-295

01Description

Services were identified presenting TLS certificates that are self-signed, issued by an untrusted authority, expired, or that do not match the hostname used to reach the service.

02Impact

Clients cannot verify the server's identity, so users and systems connecting to these services are exposed to interception by an attacker who presents their own certificate. Users who routinely click through certificate warnings become easier targets for phishing and interception.

03Severity

Typically

Low

Typically Low. Low for internal or administrative services. Medium on public, user-facing services, as it trains users to ignore certificate warnings and enables interception.

04How to verify

  1. 1Retrieve each certificate and check issuer, validity dates and subject alternative names.
  2. 2Confirm whether the issuing authority is trusted by standard client trust stores or the organization's internal PKI.
  3. 3Record expiry dates for certificates nearing expiry as well as those already expired.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Replace public-facing certificates with ones issued by a publicly trusted certificate authority; automate renewal with ACME where possible.
  2. 2Issue internal service certificates from an internal PKI trusted by managed devices.
  3. 3Monitor certificate expiry centrally and alert well ahead of expiry.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo