Openshift/router: openshift/router: mtls client certificate spoofing via unstripped x-ssl-client headers on http frontend
- 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
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in the OpenShift Router. When a Route has `insecureEdgeTerminationPolicy` set to Allow, the HTTP frontend does not remove `X-SSL-Client-*` headers from incoming requests. This allows an unauthenticated attacker to send plain HTTP requests with crafted `X-SSL-Client-*` headers. As a result, backends relying on these headers for mutual TLS (Transport Layer Security) authentication can be bypassed, enabling the attacker to impersonate client certificate identities.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- openshift4/ose-haproxy-router
Version range not reported
- openshift4/ose-haproxy-router
Version range not reported
- openshift4/ose-haproxy-router
Version range not reported
- openshift4/ose-haproxy-router
Version range not reported
- openshift4/ose-haproxy-router-rhel9
Version range not reported
- openshift4/ose-haproxy-router-rhel9
Version range not reported
- openshift4/ose-haproxy-router-rhel9
Version range not reported
- openshift4/ose-haproxy-router-rhel9
Version range not reported
- openshift4/ose-haproxy-router-rhel9
Version range not reported
- openshift4/ose-haproxy-router-rhel9
Version range not reported
- openshift4/ose-haproxy-router-rhel9
Version range not reported