CVE-2020-26877
Apifest Oauth 2.0 Server vulnerability
ApiFest OAuth 2.0 Server 0.3.1 does not validate the redirect URI in accordance with RFC 6749 and is susceptible to an open redirector attack. Specifically, it directly sends an authorization code to the redirect URI submitted with the authorization request, without checking whether the redirect URI is registered by the client who initiated the request. This allows an attacker to craft a request with a manipulated redirect URI (redirect_uri parameter), which is under the attacker's control, and consequently obtain the leaked authorization code when the server redirects the client to the manipulated redirect URI with an authorization code. NOTE: this is similar to CVE-2019-3778.
Affected products
Oauth 2.0 Server. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Apifest Oauth 2.0 Server runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.apifest.org/index.html · Vendor Advisory
- github.com/apifest/apifest-oauth20 · Third Party Advisory
- tools.ietf.org/html/rfc6749#section-3.1.2.3 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-26877
- cve.org/CVERecord?id=CVE-2020-26877
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.