Attacks/Breaches
9/26/2012
03:48 PM
Connect Directly
RSS
E-Mail
50%
50%

100,000 IEEE User Passwords, IDs Exposed On Internet

IEEE admits it exposed user IDs and passwords for roughly 100,000 members, but otherwise remains mum

Questions remain following revelations that plain-text files with user credentials for nearly 100,000 members of the Institute of Electrical and Electronics Engineers (IEEE) was exposed on a publicly accessible server.

The FTP server had been left open to the Net for at least a month before the problem was discovered Sept. 18, according to Radu Dragusin, a teaching assistant at the University of Copenhagen, Denmark. The files contained password and user ID information, including some belonging to members from organizations such as NASA and Stanford University as well as corporations like Apple and Google.

Though IEEE confirmed the breach after being notified by Dragusin Sept. 24, it has remained silent about exactly why the security failures that led to the information being exposed occurred. In a statement, IEEE said it has conducted a "thorough investigation" and addressed the issue, and is currently in the process of notifying anyone who may have been affected.

"Due to several undoubtedly grave mistakes, the ieee.org account username and plaintext password of around 100,000 IEEE members were publicly available on the IEEE FTP server for at least one month," Dragusin explains in a blog post. "Furthermore, all the actions these users performed on the ieee.org website were also available. Separately, spectrum.ieee.org visitor activity is also publicly available. "

"The simplest and most important mistake on the part of the IEEE web administrators was that they failed to restrict access to their webserver logs for both ieee.org and spectrum.ieee.org allowing these to be viewed by anyone going to the address ftp://ftp.ieee.org/uploads/akamai/ (closed on September 24 around 13:00 UTC, after I reported it)," Dragusin adds. "On these logs, as is the norm, every web request was recorded (more than 376 million HTTP requests in total). Web server logs should never be publicly available, since they usually contain information that can be used to identify users."

Constant changes in an organization's environment, such as network configurations, can lead to the type of access control failure that made the IEEE breach possible, says Torsten George, vice president of worldwide marketing, for products and support for Agiliance. These errors can be addressed through continuous monitoring, he said.

It is not clear whether someone other than Dragusin accessed the data. According to him, some 411,308 of the log entries contain both usernames and passwords. Out of these, there appear to be 99,979 unique usernames.

"If leaving an FTP directory containing 100GB of logs publicly open could be a simple mistake in setting access permissions, keeping both usernames and passwords in plaintext is much more troublesome," Dragusin blogs. "Keeping a salted cryptographic hash of the password is considered best practice, since it would mitigate exactly such an access permission mistake. Also, keeping passwords in logs is inherently insecure, especially plaintext passwords, since any employee with access to logs (for the purpose of analysis, monitoring or intrusion detection) could pose a threat to the privacy of users."

In an analysis of the data, Dragusin found that the most common password used by IEEE members is '123456', with 'ieee2012' coming in not far behind.

"We have already seen a number of data breaches this year where information was stored in the clear on internet facing servers," notes Todd Thiemann, senior director of product marketing for Vormetric.

"The IEEE incident is yet another reminder that enterprises need to reevaluate what constitutes sensitive data, know where that data resides, and implement baseline security measures like access control and encryption to protect it," he adds.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
akeim1
50%
50%
akeim1,
User Rank: Apprentice
9/27/2012 | 5:17:42 PM
re: 100,000 IEEE User Passwords, IDs Exposed On Internet
why organizations are still keeping credentials in the clear is inexcusable!! Hefty fines for ANY business, per record, short of public flogging.- SHAME on IEEE!!
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.