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
Cloud Security Threats for 2021
Or Azarzar, CTO & Co-Founder of Lightspin,  12/3/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Assessing Cybersecurity Risk in Todays Enterprises
Assessing Cybersecurity Risk in Todays Enterprises
COVID-19 has created a new IT paradigm in the enterprise and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27772
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in coders/bmp.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned int`. This would most likely lead to an impact to application availability, but could po...
CVE-2020-27773
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in MagickCore/gem-private.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char` or division by zero. This would most likely lead to an impact to appli...
CVE-2020-28950
PUBLISHED: 2020-12-04
The installer of Kaspersky Anti-Ransomware Tool (KART) prior to KART 4.0 Patch C was vulnerable to a DLL hijacking attack that allowed an attacker to elevate privileges during installation process.
CVE-2020-27774
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in MagickCore/statistic.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of a too large shift for 64-bit type `ssize_t`. This would most likely lead to an impact to application availability, but co...
CVE-2020-27775
PUBLISHED: 2020-12-04
A flaw was found in ImageMagick in MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type unsigned char. This would most likely lead to an impact to application availability, but c...