Vulnerabilities / Threats
09:45 AM

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.

The source code theft involves more than just the pcAnywhere application, and Symantec Tuesday detailed all products involved. "Our investigation continues to indicate that the theft is limited to only the code for the 2006 versions of Norton Antivirus Corporate Edition; Norton Internet Security; Norton SystemWorks (Norton Utilities and Norton GoBack); and pcAnywhere," according to Symantec.

What exactly could malicious actors do with the source code to pcAnywhere? In a white paper released Tuesday, Symantec detailed the potential risks, which include breaking the encryption or encoding used by the product, which would allow attackers to launch successful man-in-the-middle attacks, through which they could steal a PC user's credentials or session information. In particular, this could allow them to steal the cryptographic key required to remotely connect to the computer. "If the cryptographic key itself is using Active Directory credentials, it is also possible for them to perpetrate other malicious activities on the network," said Symantec.

Similar types of attacks could be launched by insiders or botnets, according to the white paper. In either case, provided that attackers had broken the pcAnywhere encryption, they'd be able to intercept session details or credentials by planting a sniffer in the internal network.

Symantec said the source code stolen in 2006 accounted for approximately 5% of the code found in its Symantec AntiVirus 10.2 product. But it said that users of its 10.x and newer products--aside from pcAnywhere--"should not be in any increased danger of cyber attacks" resulting from the source code theft.

Also on the good-news front, the company said that it now thinks that the source code for Symantec Endpoint Protection 11, released in late 2007, wasn't stolen, as it first suspected. That finding will be a relief for current version 11 users, as well as for Symantec, since the product was the first to contain multiple new types of security technology--also present in its current 12.x product versions--including "heuristic protection, intrusion prevention security, firewall, application control, device control, tamper protection, redesigned core engines, as well as our Symantec Endpoint Protection Manager (SEPM)," according to Symantec.

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.)

2 of 2
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Dark Reading Tech Digest September 7, 2015
Some security flaws go beyond simple app vulnerabilities. Have you checked for these?
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-02
Buffer overflow in Canary Labs Trend Web Server before 9.5.2 allows remote attackers to execute arbitrary code via a crafted TCP packet.

Published: 2015-10-02
Cisco NX-OS 6.0(2)U6(0.46) on N3K devices allows remote authenticated users to cause a denial of service (temporary SNMP outage) via an SNMP request for an OID that does not exist, aka Bug ID CSCuw36684.

Published: 2015-10-02
Cisco Email Security Appliance (ESA) 8.5.6-106 and 9.6.0-042 allows remote authenticated users to cause a denial of service (file-descriptor consumption and device reload) via crafted HTTP requests, aka Bug ID CSCuw32211.

Published: 2015-10-01
lxc-start in lxc before 1.0.8 and 1.1.x before 1.1.4 allows local container administrators to escape AppArmor confinement via a symlink attack on a (1) mount target or (2) bind mount source.

Published: 2015-10-01
kernel_crashdump in Apport before 2.19 allows local users to cause a denial of service (disk consumption) or possibly gain privileges via a (1) symlink or (2) hard link attack on /var/crash/vmcore.log.

Dark Reading Radio
Archived Dark Reading Radio
What can the information security industry do to solve the IoT security problem? Learn more and join the conversation on the next episode of Dark Reading Radio.