Bug 1892551 (CVE-2020-25688) - CVE-2020-25688 rhacm: certificate re-use in grcuiapi and topologyapi
Summary: CVE-2020-25688 rhacm: certificate re-use in grcuiapi and topologyapi
Keywords:
Status: NEW
Alias: CVE-2020-25688
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1862477 1893081 1893082
Blocks: 1891712
TreeView+ depends on / blocked
 
Reported: 2020-10-29 06:34 UTC by Doran Moppert
Modified: 2021-02-23 16:09 UTC (History)
9 users (show)

Fixed In Version: rhacm 2.0.5, rhacm 2.1.0
Doc Type: If docs needed, set a value
Doc 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.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Doran Moppert 2020-10-29 06:34:49 UTC
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.

Release 2.0.5 and 2.1.0 are planned to fix this vulnerability, by generating a unique certificate at deployment time.


Note You need to log in before you can comment on or make changes to this bug.