GHSA-hjrh-q6pg-mh82: Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes
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.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
aws-privateca-issuerto a version that resolves this vulnerability.Fixed in v1.10.1 - Upgrade
Upgrade
AWS Private CA Connector for Kubernetes EKS add-onto a version that resolves this vulnerability.Fixed in v1.10.1-eksbuild.1 - Configuration
Update certificate requests, Certificate resources, and Ingress annotations so issuerRef.kind is present, exactly AWSPCAIssuer or AWSPCAClusterIssuer, and matches the referenced issuer.
AWS Private CA Connector for Kubernetes issuerRef.kind = AWSPCAIssuer or AWSPCAClusterIssuer