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

06:00 AM
Larry Loeb
Larry Loeb
Larry Loeb

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
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...