Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
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.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Incorrect authorization in the credential loading logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, signed by another namespace's AWS Private CA with that namespace's stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace. To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer's namespace and update the issuer's secretRef.namespace to match. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1. | |
| Title | Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) | |
| First Time appeared |
Aws
Aws aws-privateca-issuer |
|
| Weaknesses | CWE-441 CWE-639 |
|
| CPEs | cpe:2.3:a:aws:aws-privateca-issuer:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aws
Aws aws-privateca-issuer |
|
| References |
|
|
| Metrics |
cvssV3_1
|