Vulnerabilities / Threats
1/26/2012
09:45 AM
50%
50%

Symantec: Users Should Disable PCAnywhere Now

Symantec moves into damage-control mode after LulzSec leader tweets the remote-access software may be used to launch exploits.

Stop using pcAnywhere.

The recommendation that users disable or delete the software is the takeaway from a surprise security advisory issued by Symantec late Tuesday, which warns customers to "only use pcAnywhere for business-critical purposes," and even then, only after configuring the software "in a way that minimizes potential risks."

Those risks stem from the theft of Symantec source code in 2006. The worry is that attackers, after studying the code, may have found a way to crack pcAnywhere's encryption, which would allow them to use the remote-access software to remotely access any PC on which it's active. That, in turn, might give attackers access to data stored on corporate networks.

Those revelations will no doubt lead to sharp questions for information security vendor Symantec, especially given the fact that five years' time elapsed between the source code theft, and Symantec publicly confirming the breach. Indeed, the data exposure only came to light after the hacking group Lords of Dharmaraja earlier this month posted to Pastebin what it said was part of the source code for Symantec's Norton Utilities (NU).

[ Consider another potential security hole in your enterprise: Videoconferencing Systems Vulnerable To Hackers. ]

Symantec at first dismissed that claim, but on January 16, former LulzSec leader Sabu announced via Twitter: "Lords of Dharmaraja has sent #antisec Symantec source codes for 0day-plundering. All your NU+PCAnywhere base are belong to us. Release soon."

Since then, Symantec has switched into damage-control mode, and begun detailing the results of its internal investigation into the source theft, which remains ongoing. "There are no indications that customer information has been impacted or exposed at this time," according to Symantec's security bulletin.

Who's at risk? According to Symantec's security advisory, "all pcAnywhere 12.0, 12.1, and 12.5 customers are at increased risk, as well as customers using prior versions of the product." The remote-access software runs on Windows, Mac OS X, Linux, and the PocketPC platform.

Symantec's pcAnywhere has also been bundled with numerous other products, both from Symantec as well as Altiris, which Symantec acquired in 2007. In addition, said Symantec, "a remote access component of pcAnywhere, called the pcAnywhere Thin Host, is also bundled with a number of Symantec backup and security products."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5426
Published: 2014-11-27
MatrikonOPC OPC Server for DNP3 1.2.3 and earlier allows remote attackers to cause a denial of service (unhandled exception and DNP3 process crash) via a crafted message.

CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?