Researcher finds 100K passwords, user IDs, on IEEE site

Danish CS teaching assistant says he stumbled upon IEEE cache during search for research material

A Danish graduate student said he was searching for research material on an IEEE FTP server last week when he stumbled upon the usernames and passwords of about 100,000 members of the professional association.

In a blog post on Tuesday, Radu Dragusin, a teaching assistant and computer science grad student at the University of Copenhagen, said the data appears to have been publicly available for at least a month before he found it.

The login credentials freely available on the site belonged to IEEE members from organizations such as NASA, Stanford University, Apple and Google, Dragusin said.

In addition to usernames and passwords, Dragusin said he was able to access more than 100GB of web server log data containing detailed information on 350 million-plus HTTP requests made by IEEE members over one month.

By accessing the log data, he said he could inspect IEEE.org pages that were accessed by logged in members, and determine when the pages were accessed and from where.

In an email to Computerworld, Dragusin said he discovered the data when looking for free research material from IEEE.

"I was merely surfing the public IEEE FTP server to see if they have a repository of freely available research articles," Dragusin said. "If you go on the FTP server yourself, you will see that the 'uploads' directory is among the most recently modified ones, so I opened it."

The directory contained many more directories including one containing the word "Akamai," which Dragusin said he knew was the name of a well-known content delivery network. He downloaded and decompressed one of the many GNU Zipped Archive files contained in the directory and then discovered detailed web-server logs.

At that point he downloaded everything in the Akamai directory and found more than 100GB of uncompressed log data.

"This looked interesting, because logs are not supposed to be public, as they often contain personal data," Dragusin said. "As a researcher, I saw the opportunity to study the logs to gain some insights into IEEE members, many of whom are researchers and engineers."

A closer inspection of the data showed that many of the log entries contained usernames and passwords.

That finding "was highly unusual and of course transformed this into a serious data breach," he said.

According to Dragusin, the files on the FTP server had been freely accessible since at least August 17.

Information on a Russian site that indexes FTP listings suggests that similar log data was publicly available some time last year as well, he added.

The breach is embarrassing for IEEE as it's a mistake -- storing login credentials in plain text -- that novice security professionals should know to avoid.

In a statement, an IEEE spokeswoman today said the organization is aware of an incident regarding "inadvertent access to unencrypted log files containing user IDs and passwords."

"We have conducted a thorough investigation and the issue has been addressed and resolved. We are in the process of notifying those who may have been affected," the statement said.

The spokeswoman did not say how the data could be available on a public FTP server, or why it was stored in unencrypted fashion.

An IEEE alert to members (available here) said that no financial information was exposed as a result of the error.

"However, it was theoretically possible for an unauthorized third party, using your ID and your password, to have accessed your IEEE account," the alert cautioned.

As a precautionary measure, IEEE has terminated access to accounts with current passwords and users will be required to create a new one next time they attempt to log into their accounts, the statement said.

Jaikumar Vijayan covers data security and privacy issues, financial services security and e-voting for Computerworld. Follow Jaikumar on Twitter at @jaivijayan, or subscribe to Jaikumar's RSS feed . His e-mail address is jvijayan@computerworld.com.

Join the discussion
Be the first to comment on this article. Our Commenting Policies