CVE-2020-26877
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…
Does this matter?
Lower severity and a low EPSS score (0.81%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 6.1 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- EPSS
- 0.81% probability · 55th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-601
- Affected
- apifest/oauth 2.0 server
- Source
- cve@mitre.org
References
- http://www.apifest.org/index.htmlVendor Advisory
- https://github.com/apifest/apifest-oauth20Third Party Advisory
- https://tools.ietf.org/html/rfc6749#section-3.1.2.3Third Party Advisory
- http://www.apifest.org/index.htmlVendor Advisory
- https://github.com/apifest/apifest-oauth20Third Party Advisory
- https://tools.ietf.org/html/rfc6749#section-3.1.2.3Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.