製品・ソフトウェアに関する情報
OAuth2 Proxy におけるオープンリダイレクトの脆弱性
Title OAuth2 Proxy におけるオープンリダイレクトの脆弱性
Summary

OAuth2 Proxy には、オープンリダイレクトの脆弱性が存在します。

Possible impacts 情報を取得される、および情報を改ざんされる可能性があります。
Solution

ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。

Publication Date Feb. 2, 2021, midnight
Registration Date Oct. 19, 2021, 5:23 p.m.
Last Update Oct. 19, 2021, 5:23 p.m.
CVSS3.0 : 警告
Score 6.1
Vector CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CVSS2.0 : 警告
Score 5.8
Vector AV:N/AC:M/Au:N/C:P/I:P/A:N
Affected System
oauth2_proxy project
oauth2_proxy 7.0.0 未満
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
Change Log
No Changed Details Date of change
1 [2021年10月19日]
  掲載
Oct. 19, 2021, 5:23 p.m.

NVD Vulnerability Information
CVE-2021-21291
Summary

OAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. In OAuth2 Proxy before version 7.0.0, for users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect. For example, if a whitelist domain was configured for ".example.com", the intention is that subdomains of example.com are allowed. Instead, "example.com" and "badexample.com" could also match. This is fixed in version 7.0.0 onwards. As a workaround, one can disable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.

Publication Date Feb. 3, 2021, 4:15 a.m.
Registration Date Feb. 3, 2021, 10:02 a.m.
Last Update Nov. 21, 2024, 2:47 p.m.
Affected software configurations
Configuration1 or higher or less more than less than
cpe:2.3:a:oauth2_proxy_project:oauth2_proxy:*:*:*:*:*:*:*:* 7.0.0
Related information, measures and tools
Common Vulnerabilities List