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.

Application Security

9/12/2019
05:15 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Instagram Bug Put User Account Details, Phone Numbers at Risk

The vulnerability, now patched, is the latest in a series of bad news for Facebook.

A now-patched Instagram vulnerability could have exposed users' account data and phone numbers to cyberattackers, parent company Facebook confirmed in a new report from Forbes.

The bug was discovered by an Israeli hacker who goes by the handle @ZHacker13. It could have potentially been used to access user data including names, full phone numbers, and Instagram account numbers and handles – all an attacker needs to narrow their focus on a specific person.

It's the latest in a series of bad news for Facebook, which recently patched an account-takeover flaw in Instagram that would have let an attacker take over any account by resetting its password. Earlier this month, 419 million phone numbers belonging to Facebook users were found publicly accessible in a third-party database left online without password protection.

This particular vulnerability existed in Instagram's contact importer, which, when subject to brute force attacks, could grant an attacker access to the data. An attacker could use an algorithm to verify individual phone numbers to see which are linked to an Instagram account. Exploiting a second process could give them the name and number linked to the phone number, enabled by the Sync Contacts tool that lets users find their contacts on the platform.

In theory, an attacker could leverage a wealth of bots to brute force Instagram's login form and collect legitimate phone numbers, Forbes points out in its report. Instagram caps syncing to three times per day, per account; however, an attacker with enough bots could bypass this limitation. While this bug was difficult to exploit, it was possible for an attacker to build a collection of user data.

"This vulnerability further demonstrates the over-reliance of phone numbers as a strong form of authentication to digital platforms like Instagram," said Zack Allen, director of threat operations at ZeroFox, who in an email called the importance of phone numbers as identifiers on modern Internet platforms "harrowing."

"A database such as the one leaked last week with millions of phone numbers, and a vulnerability like this to tie accounts to phone numbers, sets a dangerous precedent for those vulnerable to SIM swaps," he added.

@ZHacker13 shared his findings with Facebook in early August. Facebook initially responded, saying these types of vulnerabilities, which show a given email address or phone number is linked with a specific account, are "extremely low risk." However, bugs that let an attacker figure out which user ID an email address or phone number is linked to are another story.

After further communication in which the company reportedly expressed little urgency to fix the problem, Facebook told @ZHacker13 this was "a valid issue." It has now addressed the problem; the researcher has tested his exploit and confirmed with Forbes it no longer works. There has not yet been evidence indicating account data was misused as a result of the vulnerability.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Community Projects Highlight Need for Security Volunteers."

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
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/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-25595
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. The PCI passthrough code improperly uses register data. Code paths in Xen's MSI handling have been identified that act on unsanitized values read back from device hardware registers. While devices strictly compliant with PCI specifications shouldn't be ...
CVE-2020-5783
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the login functionality does not contain any CSRF protection mechanisms.
CVE-2020-11031
PUBLISHED: 2020-09-23
In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library c...
CVE-2020-5781
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the langSelection parameter is stored in the luci configuration file (/etc/config/luci) by the authenticator.htmlauth function. When modified with arbitrary javascript, this causes a denial-of-service condition for all other users.
CVE-2020-5782
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, if a user logs in and sets the ‘wan_type’ parameter, the wan interface for the device will become unreachable, which results in a denial of service condition for devices dependent on this connection.