BOSTON (Reuters) - Security experts warn there is little Internet users can do to protect themselves from the recently uncovered “Heartbleed” bug that exposes data to hackers, at least not until vulnerable websites upgrade their software.
Researchers have observed sophisticated hacking groups conducting automated scans of the Internet in search of Web servers running a widely used Web encryption program known as OpenSSL that makes them vulnerable to the theft of data, including passwords, confidential communications and credit card numbers.
OpenSSL is used on about two-thirds of all Web servers, but the issue has gone undetected for about two years.
Kurt Baumgartner, a researcher with security software maker Kaspersky Lab, said his firm uncovered evidence on Monday that a few hacking groups believed to be involved in state-sponsored cyber espionage were running such scans shortly after news of the bug first surfaced the same day.
By Tuesday, Kaspersky had identified such scans coming from “tens” of actors, and the number increased on Wednesday after security software company Rapid7 released a free tool for conducting such scans.
“The problem is insidious,” Baumgartner said. “Now it is amateur hour. Everybody is doing it.”
OpenSSL software is used on servers that host websites but not PCs or mobile devices, so even though the bug exposes passwords and other data entered on those devices to hackers, it must be fixed by website operators.
“There is nothing users can do to fix their computers,” said Mikko Hypponen, chief research officer with security software maker F-Secure (FSC1V.HE).
Google spokeswoman Dorothy Chou told Reuters: “We fixed this bug early and Google users do not need to change their passwords.”
Ty Rogers, a spokesman for Amazon.com Inc (AMZN.O), said “Amazon.com is not affected.”
In a blogpost dated Tuesday, the company said some of its Web cloud services, which provide the underlying infrastructure for apps such as online movie-streaming service Netflix and social network Pinterest, had been vulnerable. While it said the problems had been fixed, the company urged users of those services, which are popular in particular among the tech startup community, to take extra steps such as updating software.
Kaspersky Lab’s Baumgartner noted that devices besides servers could be at risk because they run software programs with vulnerable OpenSSL code built into them.
They include versions of Cisco Systems Inc’s (CSCO.O) AnyConnect for iOS and Desktop Collaboration, Tor, OpenVPN and Viscosity from Spark Labs. The developers of those programs have either updated their software or published directions for users on how to mitigate potential attacks.
Steve Marquess, president of the OpenSSL Software Foundation, said he could not identify other computer programs that used OpenSSL code that might make devices vulnerable to attack.
Bruce Schneier, a well-known cryptologist and chief technology officer of Co3 Systems, called on Internet companies to issue new certificates and keys for encrypting Internet traffic, which would render stolen keys useless.
That will be time-consuming, said Barrett Lyon, chief technology officer of cybersecurity firm Defense.Net Inc. “There’s going to be lots of chaotic mess,” he said.
Symantec Corp (SYMC.O) and GoDaddy, two major providers of SSL technology, said they do not charge for reissuing keys.
Mark Maxey, a director with cybersecurity firm Accuvant, said it is no easy task for large organizations to implement the multiple steps to clean up the bug, which means it will take some a long time to do so.
“Due to the complexity and difficulty in upgrading many of the affected systems, this vulnerability will be on the radar for attackers for years to come,” he said.
Hypponen of F-Secure said computer users could immediately change passwords on accounts, but they would have to do so again if their operators notify them that they are vulnerable.
“Take care of the passwords that are very important to you,” he said. “Maybe change them now, maybe change them in a week. And if you are worried about your credit cards, check your credit card bills very closely.”
Reporting by Jim Finkle; Additional reporting by Joseph Menn; Editing by Leslie Adler, Dan Grebler and Mohammad Zargham