rhacm: certificate re-use in grcuiapi and topologyapi
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | rhacm | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Advanced Cluster Management for Kubernetes 2.0 for RHEL 8 | |||
| rhacm2/acm-operator-bundle:v2.0.5-5 | cpe:/a:redhat:acm:2.0::el8 | RHBA-2020:5095 | 2020-11-11T00:00:00Z |
| Red Hat Advanced Cluster Management for Kubernetes 2.1 for RHEL 8 | |||
| rhacm2/acm-must-gather-rhel8:v2.1.0-11 | cpe:/a:redhat:acm:2.1::el8 | RHEA-2020:4954 | 2020-11-05T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-18350 | A flaw was found in rhacm versions before 2.0.5 and before 2.1.0. Two internal service APIs were incorrectly provisioned using a test certificate from the source repository. This would result in all installations using the same certificates. If an attacker could observe network traffic internal to a cluster, they could use the private key to decode API requests that should be protected by TLS sessions, potentially obtaining information they would not otherwise be able to. These certificates are not used for service authentication, so no opportunity for impersonation or active MITM attacks were made possible. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.251% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.