Thorsten Tuellmann

Name of the Vulnerable Software and Affected Versions: Cohesity DataPlatform versions 6.3 prior to 6.3.1g Cohesity DataPlatform versions 6.4 up to 6.4.1c Cohesity DataPlatform versions 6.5.1 through 6.5.1b Description: The issue is related to an undocumented default cryptographic key in the Cohesity DataPlatform. This key can be used by an attacker to gain access to the Linux system in the affected versions. The `ssh key` is specifically mentioned as the vulnerable component that can provide such access. Recommendations: For versions 6.3 prior to 6.3.1g, update to version 6.3.1g or later. For versions 6.4 up to 6.4.1c, update to version 6.4.1c or later. For versions 6.5.1 through 6.5.1b, update to version 6.5.1b or later. As a temporary workaround, consider restricting access to the `ssh key` to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Cohesity DataPlatform versions 6.3 through 6.3.1g Cohesity DataPlatform versions 6.4 through 6.4.1c Cohesity DataPlatform versions 6.5.1 through 6.5.1b Description: A man-in-the-middle issue exists due to missing server authentication in the support channel of Cohesity DataPlatform. This allows an attacker to intercept the support channel UI session, potentially leading to unauthorized access or data manipulation. Recommendations: For versions 6.3 through 6.3.1g, update to a version later than 6.3.1g to resolve the issue. For versions 6.4 through 6.4.1c, update to a version later than 6.4.1c to resolve the issue. For versions 6.5.1 through 6.5.1b, update to a version later than 6.5.1b to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Cohesity DataPlatform versions prior to 6.1.1c **Description** A man-in-the-middle issue related to vCenter access was discovered. It was found that Cohesity clusters did not verify TLS certificates presented by vCenter, which could expose user credentials configured to access vCenter. **Recommendations** For versions prior to 6.1.1c, update to version 6.1.1c or later to resolve the issue. As a temporary workaround, consider restricting access to vCenter to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Rubrik CDM versions 3.x and 4.x before 4.0.4-p2 Description: A man-in-the-middle vulnerability related to vCenter access was found. This issue might expose Rubrik user credentials configured to access vCenter because Rubrik clusters did not verify TLS certificates presented by vCenter. Recommendations: For Rubrik CDM versions 3.x and 4.x before 4.0.4-p2, update to version 4.0.4-p2 or later to resolve the issue. As a temporary workaround, consider restricting access to vCenter until the update is applied.