CVE-2024-5037

HIGHNVD 7.57.5—

7.5

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.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 57.0%
KEV: Not listed

Published

June 5, 2024

Last Modified

November 21, 2024

References (17)

secalert@redhathttps://access.redhat.com/errata/RHSA-2024:4151
secalert@redhathttps://access.redhat.com/errata/RHSA-2024:4156
secalert@redhathttps://access.redhat.com/errata/RHSA-2024:4329
secalert@redhathttps://access.redhat.com/errata/RHSA-2024:4484
secalert@redhathttps://access.redhat.com/errata/RHSA-2024:5200
secalert@redhathttps://access.redhat.com/security/cve/CVE-2024-5037
secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2272339
secalert@redhathttps://github.com/kubernetes/kubernetes/pull/123540
secalert@redhathttps://github.com/openshift/telemeter/blob/a9417a6062c3a31ed78c06ea3a0613a52f2029b2/pkg/authorize/jwt/client_authorizer.go#L78
af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/errata/RHSA-2024:4151
af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/errata/RHSA-2024:4156
af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/errata/RHSA-2024:4329
af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/errata/RHSA-2024:4484
af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/security/cve/CVE-2024-5037
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=2272339

Vendor Advisories for CVE-2024-5037(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

RHSA-2024:4484
Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.13.45 bug fix and security update

Patch Availability(5)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
redhat	openshift4/ose-telemeter:v4.12.0-202408071159.p0.gc9592de.assembly.stream.el8	2024-08-19	redhat
redhat	openshift4/ose-telemeter:v4.13.0-202407081338.p0.g0634a6d.assembly.stream.el8	2024-07-17	redhat
redhat	openshift4/ose-telemeter:v4.14.0-202407021509.p0.g1f72681.assembly.stream.el8	2024-07-11	redhat
redhat	openshift4/ose-telemeter-rhel9:v4.16.0-202406200537.p0.gc1ecd10.assembly.stream.el9	2024-07-03	redhat
redhat	openshift4/ose-telemeter-rhel9:v4.15.0-202406200537.p0.g14489f7.assembly.stream.el9	2024-07-02	redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)

Go(1)

Package	Vulnerable range	Fixed in	Dependents
github.com/openshift/telemeter	—	—	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-290Authentication Bypass by Spoofing

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-24 00:34 UTCEG score recompute
2026-05-24 00:34 UTCVendor advisory
2026-05-24 00:34 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2024-5037?

CVE-2024-5037 is a high vulnerability published on June 5, 2024. 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.

When was CVE-2024-5037 disclosed?

CVE-2024-5037 was first published in the National Vulnerability Database on June 5, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2024-5037 actively exploited?

CVE-2024-5037 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2024-5037?

CVE-2024-5037 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2024-5037?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-5037, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-5037

Explore →

Is Your Infrastructure Affected by CVE-2024-5037?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2024-5037

Published

Last Modified

References (17)

Vendor Advisories for CVE-2024-5037(1)

Patch Availability(5)

Affected Packages

Weakness Classification(1)

Additional Vendor Advisories

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2024-5037?

Same vendor

Same CWE

CVE-2024-5037

📅 Published

🔄 Last Modified

🔗 References (17)

📣 Vendor Advisories for CVE-2024-5037(1)

Patch Availability(5)

Affected Packages

Weakness Classification(1)

Additional Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2024-5037?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

References (17)

Vendor Advisories for CVE-2024-5037(1)

Frequently asked(5)

Related CVEs(same vendor + same CWE)