CVE-2023-50714: The Oauth2 PKCE implementation is vulnerable
Impact What kind of vulnerability is it? Who is impacted?
Original Report:
> The Oauth2 PKCE implementation is vulnerable in 2 ways: > 1. The authCodeVerifier should be removed after usage (similar to 'authState') > 2. There is a risk for a "downgrade attack" if PKCE is being relied on for CSRF protection.
Patches Has the problem been patched? What versions should users upgrade to?
2.2.15
Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading?
not known yet.
References Are there any links users can visit to find out more?
Other sources
yii2-authclient is an extension that adds OpenID, OAuth, OAuth2 and OpenId Connect consumers for the Yii framework 2.0. In yii2-authclient prior to version 2.2.15, the Oauth2 PKCE implementation is vulnerable in 2 ways. First, the authCodeVerifier should be removed after usage (similar to authState). Second, there is a risk for a downgrade attack if PKCE is being relied on for CSRF protection. Version 2.2.15 contains a patch for the issue. No known workarounds are available.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-50714?
CVE-2023-50714 is classified with a moderate severity due to vulnerabilities in the Oauth2 PKCE implementation.
How do I fix CVE-2023-50714?
To remediate CVE-2023-50714, upgrade to version 2.2.15 or later of the yii2-authclient package.
What types of attacks are possible with CVE-2023-50714?
CVE-2023-50714 is susceptible to downgrading attacks due to improper handling of the authCodeVerifier.
Which versions of yii2-authclient are affected by CVE-2023-50714?
CVE-2023-50714 affects all versions of the yii2-authclient package up to version 2.2.15.
Who is primarily impacted by CVE-2023-50714?
Developers using the yii2-authclient package for Oauth2 PKCE authentication are primarily impacted by CVE-2023-50714.