# CVE-2023-3089: Ocp & fips mode

> Attackers may bypass FIPS compliance requirements in OpenShift when FIPS mode is enabled due to non-validated cryptographic modules.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jul 2023
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-wj5p-x3cr-46w8, RHSA-2023:3924, RHSA-2023:4471

## What is CVE-2023-3089?

CVE-2023-3089 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 5 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-521 (Weak Password Requirements), CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2023-3089?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openshift` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.0-202306251254.p0.gc43ddea.assembly.stream.el8 |
| `openshift-ansible` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.0-202306230041.p0.g74dc7b3.assembly.stream.el8 |
| `openshift-ansible-test` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.0-202306230041.p0.g74dc7b3.assembly.stream.el8 |
| `openshift-hyperkube` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.0-202306251254.p0.gc43ddea.assembly.stream.el8 |
| `openshift` | Red Hat:openshift:4.12::el9 | All versions | 0:4.12.0-202306251254.p0.gc43ddea.assembly.stream.el9 |
| `openshift-hyperkube` | Red Hat:openshift:4.12::el9 | All versions | 0:4.12.0-202306251254.p0.gc43ddea.assembly.stream.el9 |
| `openshift-serverless-clients` | Red Hat:serverless:1.0::el8 | All versions | 0:1.8.1-6.el8 |

Products: Redhat Openshift Container Platform, Redhat Openshift Container Platform for Arm64, Redhat Openshift Container Platform for Linuxone, Redhat Openshift Container Platform for Power, Redhat Openshift Container Platform Ibm Z Systems.

## How do I fix CVE-2023-3089?

Apply the vendor's patch.

## Is CVE-2023-3089 being exploited?

There is no known exploitation of CVE-2023-3089 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Openshift Container Platform

- [CVE-2020-27836](https://insights.sbomify.com/CVE-2020-27836/): Missing authorization in cluster-ingress-operator (critical 9.8)
- [CVE-2018-1085](https://insights.sbomify.com/CVE-2018-1085/): Misconfiguration in openshift-ansible (critical 9.0)
- [CVE-2026-54099](https://insights.sbomify.com/CVE-2026-54099/): Privilege escalation in Red Hat OpenShift Container Platform 4 (high 8.8)
- [CVE-2026-1784](https://insights.sbomify.com/CVE-2026-1784/): Ose-cluster-ingress-operator: remote code execution through haproxy configuration injection (high 8.8)
- [CVE-2021-20182](https://insights.sbomify.com/CVE-2021-20182/): Privilege escalation in openshift (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3089 and fix it if it is affected.

What it is: CVE-2023-3089 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 5 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3089 in the wild and no public exploit code.

Affected product: Redhat Openshift Container Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-3089/ (Markdown: https://insights.sbomify.com/CVE-2023-3089/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3089
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3089
- OSV: https://osv.dev/vulnerability/CVE-2023-3089

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3089/
Summaries are generated and may contain mistakes; the official description above is the record.