CVE-2024-5037GO-2024-2905
Openshift/telemeter: iss check during jwt authentication can be bypassed
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- telemeter
From 4.16 · fixed in 4.17
- openshift4/ose-telemeter
Version range not reported
- openshift4/ose-telemeter
Version range not reported
- openshift4/ose-telemeter
Version range not reported
- openshift4/ose-telemeter-rhel9
Version range not reported
- openshift4/ose-telemeter-rhel9
Version range not reported
- openshift-logging/opa-openshift-rhel8
Version range not reported
- rhosdt/tempo-gateway-opa-rhel8
Version range not reported
- rhosdt/tempo-gateway-opa-rhel8
Version range not reported
- github.com/openshift/telemeterGo
All versions