Oauth-proxy: open redirect via /\ and /\t bypass in post-login redirect
- 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: partial
Summary
A flaw was found in oauth-proxy. The application fails to properly validate the destination redirect parameter (`rd`) during post-login redirection. A remote attacker can exploit this vulnerability by enticing a user to follow a specially crafted link, resulting in the user being redirected to an arbitrary external website after authenticating. This open redirect can be leveraged to conduct phishing attacks or credential theft.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- openshift4/ose-oauth-proxy
Version range not reported
- openshift4/ose-oauth-proxy
Version range not reported
- openshift4/ose-oauth-proxy-rhel9
Version range not reported
- openshift4/ose-oauth-proxy-rhel9
Version range not reported
- openshift4/ose-oauth-proxy-rhel9
Version range not reported
- openshift4/ose-oauth-proxy-rhel9
Version range not reported
- openshift4/ose-oauth-proxy-rhel9
Version range not reported
- openshift4/ose-oauth-proxy-rhel9
Version range not reported
- openshift4/ose-oauth-proxy-rhel9
Version range not reported
- openshift5/ose-oauth-proxy-rhel9
Version range not reported