# CVE-2024-5037: Openshift/telemeter: iss check during jwt authentication can be bypassed

> Attackers can bypass JWT issuer checks using forged tokens in OpenShift Telemeter under specific conditions, compromising authentication integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2024
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-gc8r-pxj9-hhx3, GO-2024-2905

## What is CVE-2024-5037?

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

### Official description

A flaw was found in OpenShift's Telemeter. If certain conditions are in place, an attacker can use a forged token to bypass the issue ("iss") check during JSON web token (JWT) authentication.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2024-5037?

1 open source package ship an affected version, including github.com/openshift/telemeter. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openshift/telemeter` | Go | All versions | None |

Products: Redhat Openshift Container Platform, Redhat Openshift Distributed Tracing.

## How do I fix CVE-2024-5037?

No fix has been published for CVE-2024-5037 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5037 being exploited?

There is no known exploitation of CVE-2024-5037 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-2024-5037 and fix it if it is affected.

What it is: CVE-2024-5037 is a high-severity authentication bypass vulnerability in Redhat Openshift Container Platform, published on 5 Jun 2024. 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-2024-5037 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openshift/telemeter (Go): affected all versions; no fix listed

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-2024-5037/ (Markdown: https://insights.sbomify.com/CVE-2024-5037/index.md)
```

## Sources

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

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