# CVE-2020-25688: Hardcoded credentials in rhacm

> Attackers observing internal network traffic can decrypt API requests using hardcoded test certificates, exposing sensitive information.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xm77-mpc2-5mxx

## What is CVE-2020-25688?

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.

### Official 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2020-25688?

It affects 1 product.


Products: Redhat Advanced Cluster Management for Kubernetes.

## How do I fix CVE-2020-25688?

No fix has been published for CVE-2020-25688 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-25688 being exploited?

There is no known exploitation of CVE-2020-25688 in the wild and no public exploit code.

## Other vulnerabilities in rhacm

- [CVE-2026-4740](https://insights.sbomify.com/CVE-2026-4740/): Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation (high 8.2)
- [CVE-2023-3027](https://insights.sbomify.com/CVE-2023-3027/): Privilege escalation in RHACM (high 7.8)
- [CVE-2022-3841](https://insights.sbomify.com/CVE-2022-3841/): Server-side request forgery in RHACM (high 7.8)
- [CVE-2026-71474](https://insights.sbomify.com/CVE-2026-71474/): Insights-client-rhel9: insights-client: pull-secret bearer token written to logs on non-200 ccx response (high 7.1)
- [CVE-2026-71475](https://insights.sbomify.com/CVE-2026-71475/): Insights-client-rhel9: insights-client: spoke-controlled clusterid injected unencoded into insights api url path (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25688 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2020-25688 in the wild and no public exploit code.

Affected product: rhacm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25688/ (Markdown: https://insights.sbomify.com/CVE-2020-25688/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25688
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25688
- OSV: https://osv.dev/vulnerability/CVE-2020-25688

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25688/
Summaries are generated and may contain mistakes; the official description above is the record.