Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.10.1, 1.10.1-eksbuild.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The AWS Private CA Connector for Kubernetes (aws-privateca-issuer), including its EKS add-on, is affected by this flaw in how it resolves certificate issuers. An authenticated user could obtain certificates, including subordinate CA certificates, from a cluster-wide issuer that their approval policy should not allow them to use.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Incorrect authorization in the issuer resolution logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before v1.10.1 might allow an authenticated remote user to obtain certificates, including subordinate CA certificates, signed by a cluster-scoped AWS Private CA issuer that their approval policy does not authorize. To remediate this issue, users should upgrade aws-privateca-issuer to version v1.10.1 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.10.1-eksbuild.1, and update any certificate requests, Certificate resources, or Ingress annotations whose issuerRef.kind is missing, incorrect, or does not match the referenced issuer, since v1.10.1 requires issuerRef.kind to be exactly AWSPCAIssuer or AWSPCAClusterIssuer and to match the issuer it references.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- AWS aws-privateca-issuer
fixed in 1.10.1
- AWS aws-privateca-issuer
fixed in 1.10.1-eksbuild.1