RHEA-2020:4954
Vulnerability from csaf_redhat - Published: 2020-11-05 11:53 - Updated: 2026-06-26 21:45A flaw was found in rhacm. Two internal service APIs were incorrectly provisioned using a test certificate from the source repository which resulted 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, and potentially obtaining information they would not otherwise be able to. The highest threat from this vulnerability is to data confidentiality.
CWE-321 - Use of Hard-coded Cryptographic Key| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: 8Base-RHACM-2.1:rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64 | — |
Vendor Fix
fix
|
{
"document": {
"aggregate_severity": {
"namespace": "https://access.redhat.com/security/updates/classification/",
"text": "Low"
},
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Copyright \u00a9 Red Hat, Inc. All rights reserved.",
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "Red Hat Advanced Cluster Management for Kubernetes 2.1 General Availability release",
"title": "Topic"
},
{
"category": "general",
"text": "Red Hat Advanced Cluster Management for Kubernetes 2.1.0 images\n\nRed Hat Advanced Cluster Management for Kubernetes provides the capabilities to address common challenges that administrators and site reliability engineers face as they work across a range of public and private cloud environments. Clusters and applications are all visible and managed from a single console\u2014with security policy built in.\n\nThis advisory contains the container images for Red Hat Advanced Cluster Management for Kubernetes. See the following Release Notes documentation, which will be updated shortly for this release, for details about this release:\n\nhttps://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.1/html/release_notes/",
"title": "Details"
},
{
"category": "legal_disclaimer",
"text": "This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.",
"title": "Terms of Use"
}
],
"publisher": {
"category": "vendor",
"contact_details": "https://access.redhat.com/security/team/contact/",
"issuing_authority": "Red Hat Product Security is responsible for vulnerability handling across all Red Hat products and services.",
"name": "Red Hat Product Security",
"namespace": "https://www.redhat.com"
},
"references": [
{
"category": "self",
"summary": "https://access.redhat.com/errata/RHEA-2020:4954",
"url": "https://access.redhat.com/errata/RHEA-2020:4954"
},
{
"category": "external",
"summary": "1845755",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1845755"
},
{
"category": "external",
"summary": "1861800",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1861800"
},
{
"category": "external",
"summary": "1861801",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1861801"
},
{
"category": "external",
"summary": "1866543",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1866543"
},
{
"category": "external",
"summary": "1876969",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1876969"
},
{
"category": "external",
"summary": "1879972",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1879972"
},
{
"category": "external",
"summary": "1880039",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1880039"
},
{
"category": "external",
"summary": "1882417",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1882417"
},
{
"category": "self",
"summary": "Canonical URL",
"url": "https://security.access.redhat.com/data/csaf/v2/advisories/2020/rhea-2020_4954.json"
}
],
"title": "Red Hat Enhancement Advisory: Red Hat Advanced Cluster Management for Kubernetes version 2.1 images",
"tracking": {
"current_release_date": "2026-06-26T21:45:22+00:00",
"generator": {
"date": "2026-06-26T21:45:22+00:00",
"engine": {
"name": "Red Hat SDEngine",
"version": "5.2.6"
}
},
"id": "RHEA-2020:4954",
"initial_release_date": "2020-11-05T11:53:22+00:00",
"revision_history": [
{
"date": "2020-11-05T11:53:22+00:00",
"number": "1",
"summary": "Initial version"
},
{
"date": "2020-11-05T11:53:22+00:00",
"number": "2",
"summary": "Last updated version"
},
{
"date": "2026-06-26T21:45:22+00:00",
"number": "3",
"summary": "Last generated version"
}
],
"status": "final",
"version": "3"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_name",
"name": "Red Hat Advanced Cluster Management for Kubernetes 2.1 for RHEL 8",
"product": {
"name": "Red Hat Advanced Cluster Management for Kubernetes 2.1 for RHEL 8",
"product_id": "8Base-RHACM-2.1",
"product_identification_helper": {
"cpe": "cpe:/a:redhat:acm:2.1::el8"
}
}
}
],
"category": "product_family",
"name": "Red Hat ACM"
},
{
"branches": [
{
"category": "product_version",
"name": "rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64",
"product": {
"name": "rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64",
"product_id": "rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64",
"product_identification_helper": {
"purl": "pkg:oci/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9?arch=amd64\u0026repository_url=registry.redhat.io/rhacm2/acm-must-gather-rhel8\u0026tag=v2.1.0-11"
}
}
}
],
"category": "architecture",
"name": "amd64"
}
],
"category": "vendor",
"name": "Red Hat"
}
],
"relationships": [
{
"category": "default_component_of",
"full_product_name": {
"name": "rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.1 for RHEL 8",
"product_id": "8Base-RHACM-2.1:rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64"
},
"product_reference": "rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64",
"relates_to_product_reference": "8Base-RHACM-2.1"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2020-25688",
"cwe": {
"id": "CWE-321",
"name": "Use of Hard-coded Cryptographic Key"
},
"discovery_date": "2020-10-26T00:00:00+00:00",
"ids": [
{
"system_name": "Red Hat Bugzilla ID",
"text": "1892551"
}
],
"notes": [
{
"category": "description",
"text": "A flaw was found in rhacm. Two internal service APIs were incorrectly provisioned using a test certificate from the source repository which resulted 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, and potentially obtaining information they would not otherwise be able to. The highest threat from this vulnerability is to data confidentiality.",
"title": "Vulnerability description"
},
{
"category": "summary",
"text": "rhacm: certificate re-use in grcuiapi and topologyapi",
"title": "Vulnerability summary"
},
{
"category": "general",
"text": "The CVSS score(s) listed for this vulnerability do not reflect the associated product\u0027s status, and are included for informational purposes to better understand the severity of this vulnerability.",
"title": "CVSS score applicability"
}
],
"product_status": {
"fixed": [
"8Base-RHACM-2.1:rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64"
]
},
"references": [
{
"category": "self",
"summary": "Canonical URL",
"url": "https://access.redhat.com/security/cve/CVE-2020-25688"
},
{
"category": "external",
"summary": "RHBZ#1892551",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1892551"
},
{
"category": "external",
"summary": "https://www.cve.org/CVERecord?id=CVE-2020-25688",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-25688"
},
{
"category": "external",
"summary": "https://nvd.nist.gov/vuln/detail/CVE-2020-25688",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-25688"
}
],
"release_date": "2020-11-05T00:00:00+00:00",
"remediations": [
{
"category": "vendor_fix",
"date": "2020-11-05T11:53:22+00:00",
"details": "Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.1/html-single/install/index#installing",
"product_ids": [
"8Base-RHACM-2.1:rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64"
],
"restart_required": {
"category": "none"
},
"url": "https://access.redhat.com/errata/RHEA-2020:4954"
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "NONE",
"baseScore": 3.5,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"products": [
"8Base-RHACM-2.1:rhacm2/acm-must-gather-rhel8@sha256:223f093c40c0f867edd0c0310faa5d5996e3446e6953ef50cd41712ff78c17c9_amd64"
]
}
],
"threats": [
{
"category": "impact",
"details": "Low"
}
],
"title": "rhacm: certificate re-use in grcuiapi and topologyapi"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.