dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2023-3089

HIGH · 7.5 CVSS v3.1 Published 2023-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A compliance problem was found in the Red Hat OpenShift Container Platform. Red Hat discovered that, when FIPS mode was enabled, not all of the cryptographic modules in use were FIPS-validated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

When FIPS mode is enabled in Red Hat OpenShift Container Platform, certain cryptographic modules in use are not FIPS-validated, creating a compliance gap where the system claims FIPS compliance but utilizes non-validated crypto modules.

MitigationReview cryptographic module configurations in OpenShift, disable or replace non-FIPS-validated modules when FIPS mode is required, and consult Red Hat documentation for validated module alternatives.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.10
Openshift Container Platform For LinuxoneApplication
Affected:= 4.10= 4.11= 4.12
Openshift Container Platform For PowerApplication
Affected:= 4.10= 4.11= 4.12
Openshift Container Platform Ibm Z SystemsApplication
Affected:= 4.10= 4.11= 4.12
Openshift Container Platform For Arm64Application
Affected:= 4.10= 4.11= 4.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine if FIPS mode is enabled in the cluster
    Check the FIPS configuration status in the OpenShift cluster. In OpenShift, FIPS mode is typically enforced at the node level and can be verified by inspecting the kubelet config or node status. Run 'oc get kubelet -o yaml' or inspect the MachineConfigPool status for FIPS-enabled nodes.
    Affected if FIPS mode is enabled on the cluster and the OpenShift version is 4.10, 4.11, or 4.12 on the affected architectures (Linuxone, Power, IBM Z Systems, Arm64)
  2. Identify cryptographic modules in use when FIPS mode is active
    Review the cryptographic modules loaded or configured in the OpenShift nodes. This can be done by examining the system crypto policies and the modules actually in use on the nodes. Check /proc/crypto or the system crypto configuration files on the nodes.
    Affected if Non-FIPS-validated cryptographic modules are being used while the cluster reports FIPS compliance enabled
  3. Compare installed OpenShift version to affected range
    Run 'oc get clusterversion' to determine the exact OpenShift Container Platform version running in the cluster.
    Affected if The installed version is 4.10, 4.11, or 4.12 on any of the affected platform types (Linuxone, Power, IBM Z Systems, or Arm64)

The environment is affected if FIPS mode is enabled on Red Hat OpenShift Container Platform versions 4.10, 4.11, or 4.12 running on Linuxone, Power, IBM Z Systems, or Arm64 architectures, and non-FIPS-validated cryptographic modules are in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review cryptographic module configurations in OpenShift, disable or replace non-FIPS-validated modules when FIPS mode is required, and consult Red Hat documentation for validated module alternatives.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3089 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data