Vulnerabilities / Threats

5/3/2018
05:10 PM
50%
50%

Twitter Alerts Users to Change Passwords Due to Flaw that Stored Them Unprotected

Social media giant discovered bug in an internal system that inadvertently stored passwords in plain text.

Happy World Password Day: Twitter today alerted its 330 million users to change their passwords after it detected a flaw in one of its internal logs that stored their passwords "unmasked."

Twitter since has fixed the bug and said it has no knowledge of a breach or abuse of the information but is asking users to create new passwords just in case. The company protects passwords via the bcrypt hashing function, which basically replaces the password with a mix of random letters and numbers that are then stored in Twitter's servers.

"Due to a bug, passwords were written to an internal log before completing the hashing process. We found this error ourselves, removed the passwords, and are implementing plans to prevent this bug from happening again," Twitter said in a blog post about the exposed passwords. 

"Out of an abundance of caution, we ask that you consider changing your password on all services where you've used this password," the company said.

Read more here on what happened and how to change your Twitter password.

 

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
5/4/2018 | 4:46:43 PM
Ugh
Stuff happens, sure, but the gall on the CTO to be essentially say, in not so many words, "We didn't really have to tell you, but we're telling you out of an abundance of caution to be nice."

As I observed on my own Twitter feed, I expect social networks like FB and Twitter to abuse my data and sell/distribute it wantonly. I do NOT expect them to keep my passwords exposed in plaintext however.

Maybe we should...
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
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
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.