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

8/28/2019
05:35 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Facebook Patches Second Account-Takeover Flaw in Instagram

The password-recovery mechanism once again puts users of the photo- and video-sharing platform at risk.

Facebook has closed a potentially serious security flaw in its Instagram photo- and video-sharing platform that would have let an attacker potentially take over any Instagram account by resetting its password.

The flaw is the second major issue the company has had to address in its password-recovery mechanism in the past two months. In both instances, India-based bug hunter Laxman Muthiyah reported the issue to Facebook and collected a bounty for it.  

Muthiyah's research was prompted by a recent Facebook decision to increase payouts to researchers who discover and report account-takeover flaws and similar critical vulnerabilities in Facebook and several of its other platforms, including Instagram.

"Instagram forgot password endpoint is the first thing that came to my mind while looking for an account takeover vulnerability," Muthiyah said in a blog last month describing the first of the two vulnerabilities he recently discovered.

Like most online services, Instagram allows users who have forgotten the password to their account to regain access via a password reset process. When a user submits a password change request from a mobile device, the person receives a six-digit code from Instagram that has to be entered in order for the password to be reset. The user has to enter the passcode within 10 minutes of receiving it or request another one.

With the first vulnerability, Muthiyah found an attacker could reset passwords to any Instagram account by triggering a password change request and then trying all 1 million possible combinations of the six-digit passcode until one of them worked.

The only hurdles Muthiyah discovered he had to get around were the 10-minute time limit and another Instagram control that blocked the number of tries a user could make after around 200 failed attempts.

He found that an attacker could bypass both by trying different passcodes from a large number of IPs at the same time. He figured that in a real scenario an attacker would need 5,000 IPs each making 200 requests to hack an account. "It sounds big, but that's actually easy if you use a cloud service provider like Amazon or Google," Muthiyah wrote. He estimated the cost of carrying out such an attack would be in the range of $150.

Facebook quickly remedied the issue and paid Muthiyah $30,000 for reporting it to the company.

Second Vulnerability
But even after the fix, Muthiyah found he could still hijack Instagram accounts by exploiting another weakness in the password reset process.

In a blog this week, Muthiyah described the second vulnerability as involving a randomly generated device ID that is sent along with every password change request an Instagram user makes from his or her mobile device. The same device ID is then also used to verify the passcode.

Muthiyah said his research showed that one device ID could be used to request passcodes for different users. He found that by requesting passcodes of multiple users on the same device, he could linearly increase the probability of hacking accounts.

In total, there are 1 million possible combinations for a six-digit passcode. "If you request pass code of 100,000 users using same device ID, you can have 10 percent success rate since 100k codes are issued to the same device ID," he wrote. "If we request pass codes for 1 million users, we would be able to hack all the one million accounts easily by incrementing the pass code one by one."

Facebook paid Muthiyah $10,000 for reporting the latest bug, which it described as having to do with "insufficient protections on a recovery endpoint." The weakness, now fixed, allowed an attacker to try numerous, valid, one-time passcodes to attempt password recovery, the company said.

Eve Maler, vice president of innovation and emerging technology at ForgeRock, says the security researcher performed a white-hat function in disclosing the flaw to Facebook. "An attacker could have silently compromised untold numbers of accounts, misrepresented user content, spread misinformation, or demanded a hefty price for the return of the accounts," Maler says.

The hack involved generating mobile device passcodes dynamically in response to a challenge by Instagram during a password reset. Such account recovery processes can be the most vulnerable part of user-involved identity management, she says.

"This process is often treated as if it were similar to routine login," Maler says. In reality what needs to happen is identity proofing — or verifying that an identity credential is being issued to the correct individual, she said.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "The Right to Be Patched: How Sentient Robots Will Change InfoSec Management."

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest 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...