CVE-2020-25688
First published: Thu Oct 29 2020(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Redhat Advanced Cluster Management For Kubernetes | <2.0.5 | |
| redhat/rhacm | <2.0.5 | 2.0.5 |
| redhat/rhacm | <2.1.0 | 2.1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID?
The vulnerability ID is CVE-2020-25688.
What is the severity of CVE-2020-25688?
The severity of CVE-2020-25688 is low with a CVSS score of 3.5.
Which versions of the affected software are vulnerable to CVE-2020-25688?
Versions before 2.0.5 and before 2.1.0 of Redhat Advanced Cluster Management for Kubernetes (RHACM) are vulnerable to CVE-2020-25688.
How does CVE-2020-25688 impact the affected software?
CVE-2020-25688 allows an attacker who can observe network traffic internal to RHACM installations to access the internal service APIs using a test certificate from the source repository.
Is there a fix available for CVE-2020-25688?
Yes, remediation is available in version 2.0.5 and version 2.1.0 of RHACM.
- collector/nvd-index
- collector/redhat-bugzilla
- alias/CVE-2020-25688
- vendor/redhat
- canonical/redhat advanced cluster management for kubernetes
- package-manager/redhat