ApiFest OAuth 2.0 Server 0.3.1 URI redirect_uri

Summaryinfo

A vulnerability identified as problematic has been detected in ApiFest OAuth 2.0 Server 0.3.1. This vulnerability affects unknown code of the component URI Handler. Performing a manipulation of the argument redirect_uri results in redirect. This vulnerability was named CVE-2020-26877. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, was found in ApiFest OAuth 2.0 Server 0.3.1. This affects some unknown functionality of the component URI Handler. The manipulation of the argument redirect_uri with an unknown input leads to a redirect vulnerability. CWE is classifying the issue as CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was presented 06/29/2022. This vulnerability is uniquely identified as CVE-2020-26877 since 10/07/2020. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1204.001 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• ApiFest

Name

• OAuth 2.0 Server

Version

• 0.3.1

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion