OAuth/OpenID 2.0 privileges management

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability classified as problematic has been found in OAuth and OpenID 2.0. This affects an unknown code. The manipulation with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-269. This is going to have an impact on integrity.

The weakness was published 05/06/2014 by Wang Jing as not defined advisory (Website). The advisory is shared at tetraph.com. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The advisory points out:

It could lead to Open Redirect attacks to both clients and providers of OAuth 2.0 or OpenID. For OAuth 2.0, these attacks might jeopardize “the token” of the site users, which could be used to access user information.

The advisory contains the following remark:

The patch of this vulnerability is easier said than done. If all the third-party applications strictly adhere to using a whitelist. Then there would be no room for attacks. However, in the real world, a large number of third-party applications do not do this due to various reasons. This makes the systems based on OAuth 2.0 or OpenID highly vulnerable. An alternative solution is the providers developing a more thorough verification procedure to prevent such attacks.

The vulnerability is also documented in the databases at SecurityFocus (BID 67196) and X-Force (93031). Further details are available at tetraph.com.



CPE 2.3infoedit

CPE 2.2infoedit


Youtube: Not available anymore


VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.7

VulDB Base Score: 5.3
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍


Class: Privilege escalation
CWE: CWE-269
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍


05/02/2014 🔍
05/06/2014 +4 days 🔍
05/12/2014 +6 days 🔍
04/02/2019 +1785 days 🔍


Advisory: tetraph.com
Researcher: Wang Jing
Status: Not defined
SecurityFocus: 67196 - OAuth and OpenID Open Redirection Vulnerability
X-Force: 93031 - OAuth and OpenID open redirect, Medium Risk
OSVDB: 106567

Misc.: 🔍


Created: 05/12/2014 10:51 AM
Updated: 04/02/2019 12:18 AM
Changes: (2) source_securityfocus_date source_securityfocus_class
Complete: 🔍


No comments yet. Please log in to comment.

Do you know our Splunk app?

Download it now for free!