Vulnerabilities / Threats
1/26/2012
09:45 AM
Connect Directly
RSS
E-Mail
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
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-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3587
Published: 2014-08-22
Integer overflow in the cdf_read_property_info function in cdf.c in file through 5.19, as used in the Fileinfo component in PHP before 5.4.32 and 5.5.x before 5.5.16, allows remote attackers to cause a denial of service (application crash) via a crafted CDF file. NOTE: this vulnerability exists bec...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.