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

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18986
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 allow attackers to brute-force (guess) valid usernames by using the 'forgot password' functionality as it returns distinct messages for invalid password and non-existing users.
CVE-2019-18981
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 lacks an Access Denied outcome for a certain scenario of an incorrect recipient ID of a notification.
CVE-2019-18982
PUBLISHED: 2019-11-15
bundles/AdminBundle/Controller/Admin/EmailController.php in Pimcore before 6.3.0 allows script execution in the Email Log preview window because of the lack of a Content-Security-Policy header.
CVE-2019-18985
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 lacks brute force protection for the 2FA token.
CVE-2019-18928
PUBLISHED: 2019-11-15
Cyrus IMAP 2.5.x before 2.5.14 and 3.x before 3.0.12 allows privilege escalation because an HTTP request may be interpreted in the authentication context of an unrelated previous request that arrived over the same connection.