{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25688 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25688 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25688 is a low-severity vulnerability in rhacm, published on 23 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25688 and fix it if it is affected.\n\nWhat it is: CVE-2020-25688 is a low-severity vulnerability in rhacm, published on 23 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-25688 in the wild and no public exploit code.\n\nAffected product: rhacm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-25688/ (Markdown: https://insights.sbomify.com/CVE-2020-25688/index.md)","id":"CVE-2020-25688","markdown":"https://insights.sbomify.com/CVE-2020-25688/index.md","name":"CVE-2020-25688","record":{"aliases":["GHSA-xm77-mpc2-5mxx"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Red Hat Advanced Cluster Management","requires_auth":"low_privilege","summary":"Attackers observing internal network traffic can decrypt API requests using hardcoded test certificates, exposing sensitive information.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"advanced_cluster_management_for_kubernetes","vendor":"redhat"}],"cvss":{"score":3.5,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in rhacm","id":"CVE-2020-25688","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Uncontrolled Resource Consumption in WildFly","id":"CVE-2020-25689"},"packages":[],"prev":{"headline":"Memory corruption in dnsmasq","id":"CVE-2020-25687"},"products":["rhacm"],"published":"2020-11-23","related":[{"cvss_score":8.2,"headline":"Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation","id":"CVE-2026-4740","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":7.8,"headline":"Privilege escalation in RHACM","id":"CVE-2023-3027","kev_date_added":null,"published":"2023-06-05"},{"cvss_score":7.8,"headline":"Server-side request forgery in RHACM","id":"CVE-2022-3841","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":7.1,"headline":"Insights-client-rhel9: insights-client: pull-secret bearer token written to logs on non-200 ccx response","id":"CVE-2026-71474","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":6.8,"headline":"Insights-client-rhel9: insights-client: spoke-controlled clusterid injected unencoded into insights api url path","id":"CVE-2026-71475","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":6.5,"headline":"Insights-client: insights-client: clusterrole grants cluster-wide secrets get/list/watch beyond least privilege","id":"CVE-2026-71846","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":6.5,"headline":"SQL injection in Red Hat Advanced Cluster Management for Kubernetes","id":"CVE-2022-2238","kev_date_added":null,"published":"2022-09-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers observing internal network traffic can decrypt API requests using hardcoded test certificates, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2020-25688/"}