Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| AWS | aws-privateca-issuer | unaffected |
|
||||||
| AWS | aws-privateca-issuer | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aws | Aws-privateca-issuer |
|
||||||||
| Aws | Aws-privateca-issuer |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.170% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes | |
| First Time appeared |
Aws
Aws aws-privateca-issuer |
|
| Weaknesses | CWE-863 | |
| CPEs | cpe:2.3:a:aws:aws-privateca-issuer:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aws
Aws aws-privateca-issuer |
|
| References |
| |
| Metrics |
cvssV3_1
|