CVE-2020-26877
ApiFest OAuth 2.0 Server Open Redirector
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.
INFO
Published Date :
June 29, 2022, 2:15 p.m.
Last Modified :
July 8, 2022, 4:21 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
2.7
Exploitability Score :
2.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2020-26877.
| URL | Resource |
|---|---|
| http://www.apifest.org/index.html | Vendor Advisory |
| https://github.com/apifest/apifest-oauth20 | Third Party Advisory |
| https://tools.ietf.org/html/rfc6749#section-3.1.2.3 | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2020-26877 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2020-26877 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Jul. 08, 2022
Action Type Old Value New Value Added CVSS V2 Metadata Victim must voluntarily interact with attack mechanism Added CVSS V2 NIST (AV:N/AC:M/Au:N/C:P/I:P/A:N) Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Changed Reference Type http://www.apifest.org/index.html No Types Assigned http://www.apifest.org/index.html Vendor Advisory Changed Reference Type https://github.com/apifest/apifest-oauth20 No Types Assigned https://github.com/apifest/apifest-oauth20 Third Party Advisory Changed Reference Type https://tools.ietf.org/html/rfc6749#section-3.1.2.3 No Types Assigned https://tools.ietf.org/html/rfc6749#section-3.1.2.3 Third Party Advisory Added CWE NIST CWE-601 Added CPE Configuration OR *cpe:2.3:a:apifest:oauth_2.0_server:0.3.1:*:*:*:*:*:*:*
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2020-26877 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2020-26877
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.07 }} 0.00%
score
0.29215
percentile