Skip to main content
InfoTLSOWASP A02:2021CWE-295

How to fix: Certificate covers an unusually large number of names

The leaf certificate lists more than fifty Subject Alternative Names on one key. A single certificate and a single private key therefore cover a large set of hostnames.

Why it matters

Every name on the certificate shares one private key, so a key compromise affects all of them simultaneously and a revocation forced by any one of them takes all of them offline together. Where the names belong to different customers or business units, the SAN list also discloses who else is hosted behind the same endpoint.

Large SAN lists are normal on shared hosting and on some CDN configurations, where a single certificate fronts many tenants, which is why this is informational rather than a defect. It is worth surfacing because it describes shared fate: the blast radius of a rotation or an emergency revocation is every name in the list, not just yours.

How to fix it

  1. 1Confirm the shared certificate is a deliberate choice rather than an artifact of how provisioning works.
  2. 2Where names span separate trust domains or customers, issue per-domain certificates so a compromise stays contained.
  3. 3If the certificate is provided by a hosting platform, check what its revocation and rotation process would mean for your own availability.

Code examples

List the names on the certificate

bash
openssl s_client -connect example.com:443 </dev/null 2>/dev/null \
  | openssl x509 -noout -ext subjectAltName \
  | tr "," "\n" | wc -l

References

Detected automatically by VulnRadar. The check id is tls-cert-san-count-excessive, stable across every scan so you can filter or diff on it.

See every tls check

Questions

How severe is Certificate covers an unusually large number of names?
VulnRadar rates this info 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-san-count-excessive, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Certificate covers an unusually large number of names 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.

Propose a checkHow a check is built

Scan your own site for certificate covers an unusually large number of names

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Certificate covers an unusually large number of names | VulnRadar