Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Network Security

12/5/2019
06:00 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Azure OAuth 2.0 Vulnerability Grabs Tokens

Security firm CyberArk is now finally able to discuss a major OAuth 2.0 vulnerability that affects Microsoft Azure web services.

Omer Tsarfati and his team at security firm CyberArk are now finally able to discuss a major OAuth 2.0 vulnerability that affects Microsoft Azure web services which they have been sitting on since October, according to their timeline.

To appreciate the problem, it's needed to step back a bit and consider how OAuth functions in the first place.

OAuth is a protocol used for authorization. End users can grant websites or applications access to their information from other websites without having to give the requesting website access to app secrets or passwords. It is widely used by many companies because it works fairly well in most situations.

A permanent "refresh" token is used in the protocol to validate identification and obtain an "access" token.

But, as CyberArk puts it, "The protocol itself is well built and secured, but a wrong implementation or inappropriate usage and configuration can have a colossal impact."

Certain of Microsoft's OAuth2.0 applications (including Portfolios, O365 Secure Score and Microsoft Service Trust) will give unquestioning trust to the white-listed domains and sub-domains they use. These domains can be registered by anyone (including an attacker) and Microsoft does not maintain a central registry of them. The app's trust can be misapplied to a false but yet trusted domain. Use of these apps is mandated in the Microsoft Account's approved applications portal.

To make things even more difficult for the security response to this vulnerability, these apps are allowed to ask for an "access_token." This token functions in the protocol as a session identifier, and is needed to actually implement an action on behalf of the user.

The combination of these two factors being active at the same time meets the requirements needed to enable an action with the user's permissions -- including gaining access to Azure resources, AD resources and more.

This means that a user encountering a specially-crafted link could initiate an OAuth workflow in Azure that ends up grabbing the user's access tokens which then allows other data to be compromised, especially if the token is functionally a privileged credential.

CyberArk recommends some mitigation steps that can be done along with the "fix" that Microsoft has issued, according to CyberArk, on 11/19/2019. They are:

  • "Make sure that all the trusted redirect URIs configured in the application are under your ownership. \r\n
  • Remove unnecessary redirect URIs.\r\n
  • Make sure the permissions that the OAuth application asks for are the least privileged one it needs.\r\n
  • Disable non-used applications."

This situation points how how security in the cloud may take unexpected turns. Vulnerabilities can arise from a myriad of sources when they are combined together in one project, and an approach that can get to the needed granularity of individual elements used in the resultant can greatly aid in the detection of malicious outcomes.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Enterprise Cybersecurity Plans in a Post-Pandemic World
Download the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-33600
PUBLISHED: 2021-09-28
A denial-of-service (DoS) vulnerability was discovered in the web user interface of F-Secure Internet Gatekeeper. The vulnerability occurs because of an attacker can trigger assertion via malformed HTTP packet to web interface. An unauthenticated attacker could exploit this vulnerability by sending ...
CVE-2021-33601
PUBLISHED: 2021-09-28
A vulnerability was discovered in the web user interface of F-Secure Internet Gatekeeper. An authenticated user can modify settings through the web user interface in a way that could lead to an arbitrary code execution on the F-Secure Internet Gatekeeper server.
CVE-2021-36165
PUBLISHED: 2021-09-28
RICON Industrial Cellular Router S9922L 16.10.3(3794) is affected by cleartext storage of sensitive information and sends username and password as base64.
CVE-2020-20691
PUBLISHED: 2021-09-27
An issue in Monstra CMS v3.0.4 allows attackers to execute arbitrary web scripts or HTML via bypassing the file extension filter and uploading crafted HTML files.
CVE-2020-20692
PUBLISHED: 2021-09-27
GilaCMS v1.11.4 was discovered to contain a SQL injection vulnerability via the $_GET parameter in /src/core/controllers/cm.php.