Risk
2/1/2012
11:20 AM
Connect Directly
RSS
E-Mail
50%
50%

Symantec Patches PCAnywhere, But Should You Delete?

Symantec says hotfix 'eliminates known vulnerabilities,' but hackers could use source code to exploit unknown holes. Some users will want to delete the app entirely.

Symantec has patched its pcAnywhere software, after reports began surfacing that hacktivists had gotten their hands on the source code for the remote-access tool.

Symantec's hotfixes, released last week, will update pcAnywhere versions 12.0, 12.1, 12.5 (including SP1, SP2, and SP3), eliminating all known vulnerabilities in the software. Symantec said the fixes are also compatible with the November 2011 patch it pushed to troubleshoot startup errors in its pcAnywhere plug-in for Windows (aka Symantec pcA Agent) version 12.6.65.

"We recommend installing these patches as quickly as possible if you have pcAnywhere installed," said Wolfgang Kandek, CTO of Qualys, in a blog post. A Symantec spokesman said via email that "the vulnerabilities that have been identified and patched were specific to the Windows version of pcAnywhere."

[ Protect your corporate data from hackers and insider threats. See 10 SharePoint Security Mistakes You Probably Make. ]

Symantec had rushed to patch pcAnywhere after Lords of Dharmaraja, a hacktivist group, apparently shared stolen Symantec source code with the hacktivist collective known as Anonymous.

That revelation led Symantec to confirm that some of its source code had apparently been stolen in a 2006 hack attack. While the company knew that there had been a "security incident" then, it had failed to spot that source code had been stolen. Furthermore, Symantec spokesman Cris Paden told Wired last week that it's unclear when Lords of Dharmaraja may have come into possession of the code.

Regardless, the worry now is that with the source code in hand, attackers might be able--or might have already been able--to find previously unknown vulnerabilities in pcAnywhere that could be exploited, allowing them to remotely access any machine on which the software was installed and enabled. Accordingly, Symantec had taken the unusual step of recommending that all pcAnywhere users disable or delete the software from their PCs until a patch was released.

With a patch now available, products that will require updating include all supported versions of pcAnywhere, as well as versions of pcAnywhere that ship as part of the Altiris IT Management Suite (7.x) and the Altiris Client Management Suite (7.x). Remote pcAnywhere, which ships with Altiris Deployment Solution 7.1, is also at risk. Symantec said that the Altiris products themselves were otherwise not at risk.

But even with Symantec's new pcAnywhere patches, is the product now safe to use? Symantec has said its hotfix "eliminates known vulnerabilities." The threat from having potential attackers possess the source code, however, is precisely that they would spot unknown vulnerabilities to exploit.

When assessing the risk posed by pcAnywhere, note that the presence of pcAnywhere on a system is not necessarily cause for security concern. "Symantec pcAnywhere is shipped separately or as an optional bundled application along with other Symantec products. Because of this, pcAnywhere could be present on a system but neither configured nor enabled," said Symantec.

If pcAnywhere is present on a PC but not configured nor enabled, then it's not vulnerable to being exploited. Even so, in such cases, it's best to delete the software. "If customers do not require the use of remote access capabilities, Symantec pcAnywhere should not be enabled. If installed but not required, it can be uninstalled from the system," according to Symantec's security advisory.

For businesses that don't want to use pcAnywhere but can't uninstall it, Symantec has outlined several security steps that they should follow. According to Kandek, Symantec advised users to "[move] Internet exposed pcAnywhere installations behind a VPN gateway, block standard pcAnywhere ports 5631 and 5632 on the firewall, and disable the auto-startup of pcAnywhere."

But given the potential power of remote-access tools, especially in the hands of someone with malicious intentions, security experts recommend not just deactivating such tools when not required, but deleting them entirely. "Personally I am a big fan of uninstalling unnecessary software, and it is always sound advice to minimize one's software footprint and related attack surface," said Kandek.

For example, the 2008 Verizon data breach investigations report, which reviewed 90 forensic investigations, found that about 40% of attacks were executed using poorly secured remote-access or system management tools, which refers "to applications such as Windows RDP, Citrix, VNC, and pcAnywhere, but also telnet and SSH," said Kandek.

"Attackers scan for these applications on the Internet and log in using default or easily guessable passwords. Once on the machine they install a malware--i.e. a backdoor and a sniffing--application, if necessary using a local exploit to become administrator or root," he said. Once on the machine, the malware can be used to automatically record keystrokes and troll for interesting data, and then relay this data back to the attacker.

It's no longer a matter of if you get hacked, but when. In this special retrospective of news coverage, Monitoring Tools And Logs Make All The Difference, Dark Reading takes a look at ways to measure your security posture and the challenges that lie ahead with the emerging threat landscape. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
lizboal1
50%
50%
lizboal1,
User Rank: Apprentice
2/3/2012 | 2:20:53 PM
re: Symantec Patches PCAnywhere, But Should You Delete?
In response to "40% of attacks were executed using poorly secured remote-access or system management tools" there is a way to ensure your remote support tool is safe from hackers. Bomgar CEO Joel Bomgar says in this blog post (http://community.bomgar.com/bl... that secure remote support comes down to four things: Architecture, Authentication, Access Controls, and Audit.

(Full disclosure: I work at Bomgar)
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.