# CVE-2022-3259: Openshift 4.9 does not use HTTP Strict Transport Security (HSTS) which may allow man-in-the-middle (MITM) attacks.


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-j6j9-rh67-v2gm

## What is CVE-2022-3259?

CVE-2022-3259 is a high-severity vulnerability in Redhat Openshift, published on 9 Dec 2022. 

### Official description

Openshift 4.9 does not use HTTP Strict Transport Security (HSTS) which may allow man-in-the-middle (MITM) attacks.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2022-3259?

It affects 1 product.


Products: Redhat Openshift.

## How do I fix CVE-2022-3259?

Upgrade to a fixed version.

## Is CVE-2022-3259 being exploited?

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

## Other vulnerabilities in Redhat Openshift

- [CVE-2014-3496](https://insights.sbomify.com/CVE-2014-3496/): Command injection in n/a (critical 10.0)
- [CVE-2014-0234](https://insights.sbomify.com/CVE-2014-0234/): Hardcoded credentials in Red Hat OpenShift Enterprise (critical 9.8)
- [CVE-2013-2060](https://insights.sbomify.com/CVE-2013-2060/): Command injection in OpenShift Origin (critical 9.8)
- [CVE-2013-4561](https://insights.sbomify.com/CVE-2013-4561/): Path traversal in openshift-origin-msg-node-mcollective (critical 9.1)
- [CVE-2014-0163](https://insights.sbomify.com/CVE-2014-0163/): Command injection in Openshift (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3259 and fix it if it is affected.

What it is: CVE-2022-3259 is a high-severity vulnerability in Redhat Openshift, published on 9 Dec 2022. 
Exploitation: There is no known exploitation of CVE-2022-3259 in the wild and no public exploit code.

Affected product: Redhat Openshift. 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-2022-3259/ (Markdown: https://insights.sbomify.com/CVE-2022-3259/index.md)
```

## Sources

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

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