CVE-2020-26877
Last modified
CVE-2020-26877 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. 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. EPSS estimates a 0.66% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apifest | Oauth 2.0 Server | 0.3.1 |
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
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-26877?
How severe is CVE-2020-26877?
How do I fix CVE-2020-26877?
Are you affected by CVE-2020-26877?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
