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.

Vulnerabilities / Threats

6/1/2020
05:10 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Apple Pays Researcher $100,000 for Critical Vulnerability

Apple has fixed a flaw in the "Sign in with Apple" feature that could have enabled attackers to break into user accounts for third-party services.

Apple has paid security researcher Bhavuk Jain $100,000 for the discovery of a critical flaw in its "Sign in with Apple" feature. The now-patched vulnerability, if exploited, could have let attackers bypass authentication and take over user accounts for third-party applications.

The feature was introduced in iOS 13 as a faster and more private means of signing into apps and websites. Instead of authenticating with social accounts or filling out forms, users can log in with Apple ID and Apple will provide developers with a random ID. Even when asked for a name or email address, users can share a random email address to keep their personal email private.

Back in April, Jain found a critical bug in Sign in with Apple that affected the third-party apps using it without implementing their own security protections. "This bug could have resulted in a full account takeover of user accounts on that third party application irrespective of a victim having a valid Apple ID or not," he explains in a blog post detailing the vulnerability.

In addition to paying Jain a bounty, Apple conducted an investigation into its server logs and confirmed this flaw was not used to compromise any user accounts.

Sign in with Apple works similarly to OAuth 2.0. There are two ways to authenticate a user: with a JSON Web Token (JWT) or a code generated by the Apple server, which is then used to create a JWT which is then used to validate a user's identity. When granting authorization, Apple gives users the option to share their Apple Email ID with a third-party application. If a user decides to hide his or her Email ID, Apple generates a user-specific Apple relay Email ID to share with the app.

Depending on what the user selects, after successful authorization, Apple creates a JWT containing the relay Email ID. This is then used by the third-party application to authenticate the user. Jain discovered that while Apple asks users to log in to their Apple account before generating the request, it did not validate if a JWT request came from the same user account before logging them in.

"I found I could request JWTs for any Email ID from Apple and when the signature of these tokens was verified using Apple's public key, they showed as valid," Jain writes in his blog post. "This means an attacker could forge a JWT by linking any Email ID to it and gaining access to the victim's account."

Jain confirmed with The Hacker News that this vulnerability could be exploited for users who had chosen to hide their email ID from third-party applications. An attacker could also use this vulnerability to create a new user account with the victim's Apple ID, he adds.

In his writeup, Jain says the impact of this bug is "quite critical" because it could enable full account takeover if exploited. Many developers have integrated Sign in with Apple because it's mandatory for applications that support authentication via other social apps. Popular apps that use the feature include Dropbox, Spotify, Airbnb, and Giphy. These apps were not tested, Jain says, but they could have been vulnerable to account takeover if there were no other security measures in place when verifying a user.

Related Content:

 
 
 
 
 
 
Learn from industry experts in a setting that is conducive to interaction and conversation about how to prepare for that "really  bad day" in cybersecurity. Click for more information and to register


Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
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
Video
Cartoon
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
CVE-2020-15208
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 ...
CVE-2020-15209
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....
CVE-2020-15210
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 ...
CVE-2020-15211
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...
CVE-2020-15212
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...