Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cert Manager allows the creation of Illegal wilcard SANs #1620

Open
chuck-alt-delete opened this issue Jan 7, 2025 · 0 comments
Open

Cert Manager allows the creation of Illegal wilcard SANs #1620

chuck-alt-delete opened this issue Jan 7, 2025 · 0 comments

Comments

@chuck-alt-delete
Copy link

chuck-alt-delete commented Jan 7, 2025

Apologies if this isn't a cert-manager issue per se. I have a client using cert-manager who created a certificate with wildcard SAN using *-, which is not a legal DNS wildcard, as per RFC 44592.

Using keytool -list -v keystore.jks, we can see the illegal SAN that uses *-

SubjectAlternativeName [
  DNSName: my.example.com
  DNSName: *-my.example.com
]

If I try to create my own certificate with *- locally using using keytool, I correctly get an error:

keytool error: java.lang.RuntimeException: java.io.IOException: DNSName components must begin with a letter, digit, or the first component can have only a wildcard character *

How is it possible cert-manager issued a certificate with an illegal SAN? Is this a bug in cert-manager, or on the issuer side?

Apologies if I misunderstood anything critical. I'm just trying to understand how this could have happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant