FIPS compliance loss via unvalidated Go cryptography
Published Jul 5, 2023 · Updated Oct 24, 2024
Cryptographic compliance failure in Red Hat OpenShift Container Platform 4.10 through 4.12 causes FIPS-mode clusters to use unvalidated modules. Affected Go-based platform, operator, and layered-product components were built without configuration that routes cryptographic operations through FIPS-validated OpenSSL. The condition exists only on clusters installed with FIPS mode enabled; data remained encrypted, but unpatched deployments cannot claim FIPS compliance.
Summary
What happened
Cryptographic compliance failure in Red Hat OpenShift Container Platform 4.10 through 4.12 causes FIPS-mode clusters to use unvalidated modules. Affected Go-based platform, operator, and layered-product components were built without configuration that routes cryptographic operations through FIPS-validated OpenSSL. The condition exists only on clusters installed with FIPS mode enabled; data remained encrypted, but unpatched deployments cannot claim FIPS compliance.
The record
- CVE
- CVE-2023-3089
- Published
- Jul 5, 2023
- Updated
- Oct 24, 2024
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Virtualization
- Classifications
- CWE-327
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 5, 2023CVE publishedPublication date reported by the CVE source.
- Oct 24, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo