Facebook API 2.1 /oauth/authorize response_type/client_id/redirect_uri
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Facebook API 2.1. The impacted element is an unknown function of the file /oauth/authorize. This manipulation of the argument response_type/client_id/redirect_uri causes redirect. Furthermore, there is an exploit available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as critical was found in Facebook API 2.1 (Social Network Software). Affected by this vulnerability is some unknown processing of the file /oauth/authorize. The manipulation of the argument response_type/client_id/redirect_uri with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 05/01/2016. The weakness was shared 10/10/2016 as VL-ID 1972 as confirmed advisory (Website). It is possible to read the advisory at vulnerability-lab.com. The vendor cooperated in the coordination of the public release. The attack can be launched remotely. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1204.001 according to MITRE ATT&CK.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at vulnerability-lab.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 159 days. During that time the estimated underground price was around $25k-$100k.
Applying a patch is able to eliminate this problem. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: RedirectCWE: CWE-601
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
05/01/2016 🔍05/03/2016 🔍
05/08/2016 🔍
10/07/2016 🔍
10/10/2016 🔍
10/10/2016 🔍
10/12/2016 🔍
05/07/2019 🔍
Sources
Advisory: VL-ID 1972Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-92539
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/12/2016 09:47Updated: 05/07/2019 16:29
Changes: 10/12/2016 09:47 (51), 05/07/2019 16:29 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.