Symantec tells users: Stop using pcAnywhere -
#1
Original Poster


Join Date: Jan 2010
Location: New York and Vienna
Programs: PA WorldPass Platinum, AA, DL, LH. GHA Black, SPG and HHonors Gold
Posts: 3,872
Many travelers use pcAnywhere to get access to other computers.
There was a security breach (in 2006, believe it or not) and the code has clearly been compromised.
Other products such as LogMeIn are not impacted by this.
If you use pcAnywhere, both Symantec (the maker of pcAnywhere) and I would strongly advise that you immediately switch to another program.
There was a security breach (in 2006, believe it or not) and the code has clearly been compromised.
Other products such as LogMeIn are not impacted by this.
If you use pcAnywhere, both Symantec (the maker of pcAnywhere) and I would strongly advise that you immediately switch to another program.
#2
FlyerTalk Evangelist




Join Date: Sep 2000
Programs: BA, AA, DL, KLM, UA
Posts: 37,489
FWIW; the security breach wasn't in 2006 - the code recently stolen was claimed to be FROM 2006 and applies to the xxx 2006 versions of the programs.
At first Symantec tried to brush it off, but yesterday they changed their tone. To me, losing your source code as a security company is probably one of the worst things you could ever do.
At first Symantec tried to brush it off, but yesterday they changed their tone. To me, losing your source code as a security company is probably one of the worst things you could ever do.
#3
Original Poster


Join Date: Jan 2010
Location: New York and Vienna
Programs: PA WorldPass Platinum, AA, DL, LH. GHA Black, SPG and HHonors Gold
Posts: 3,872
#4
In Memoriam
Join Date: Feb 2000
Location: Easton, CT, USA
Programs: ua prem exec, Former hilton diamond
Posts: 31,801
On their website they are now saying the code was taken in 2006. It's good it only took them five or six years to notice, though they state they have teken steps since then to prevent it from happening again, so I bet they did know, but did not tell anybody they were exposed:
January 26, 2012, 12:50 PST
Symantec can confirm that a segment of its source code has been accessed. Upon investigation of the claims made by Anonymous regarding source code disclosure, Symantec believes that the disclosure was the result of a theft of source code that occurred in 2006. Since 2006, Symantec has instituted a number of policies and procedures to prevent a similar incident from occurring.
Furthermore, there are no indications that customer information has been impacted or exposed at this time.
The rest of the release is here
http://www.symantec.com/theme.jsp?th...us-code-claims
For a company that's business is doom and gloom, one would think they would have been all over this and not waited all this time for another group to announce there was an issue.
January 26, 2012, 12:50 PST
Symantec can confirm that a segment of its source code has been accessed. Upon investigation of the claims made by Anonymous regarding source code disclosure, Symantec believes that the disclosure was the result of a theft of source code that occurred in 2006. Since 2006, Symantec has instituted a number of policies and procedures to prevent a similar incident from occurring.
Furthermore, there are no indications that customer information has been impacted or exposed at this time.
The rest of the release is here
http://www.symantec.com/theme.jsp?th...us-code-claims
For a company that's business is doom and gloom, one would think they would have been all over this and not waited all this time for another group to announce there was an issue.
#5
Join Date: Sep 2011
Location: BOS
Posts: 519
There's nothing inherently insecure about source code being publicly available.
The problem is that attackers now have visibility into the poor coding skills ofSymantec and are now able to craft new attacks. Had the source code been available all along, things like this wouldn't really be an issue. Symantec is probably aware of existing vulnerabilities that they didn't take the time to fix, but now might be obvious to a skilled coder. Bad, bad, bad.
Plenty of security software is open source, and available for all to see. See: SSH, OpenSSL, and GPG. OpenSSL powers many many many many web sites (e.g., Google, Amazon, and others). It's what encrypts your credit card data for these sites, and it's source code is available to everyone.
The Linux OS is available open source, and when critical vulnerabilities are found, they are fixed...in minutes or hours, not weeks or months like it takes Microsoft and Apple. Or I guess not at all by Symantec.
#6
Original Poster


Join Date: Jan 2010
Location: New York and Vienna
Programs: PA WorldPass Platinum, AA, DL, LH. GHA Black, SPG and HHonors Gold
Posts: 3,872
I strongly disagree.
There's nothing inherently insecure about source code being publicly available.
The problem is that attackers now have visibility into the poor coding skills ofSymantec and are now able to craft new attacks. Had the source code been available all along, things like this wouldn't really be an issue. Symantec is probably aware of existing vulnerabilities that they didn't take the time to fix, but now might be obvious to a skilled coder. Bad, bad, bad.
Plenty of security software is open source, and available for all to see. See: SSH, OpenSSL, and GPG. OpenSSL powers many many many many web sites (e.g., Google, Amazon, and others). It's what encrypts your credit card data for these sites, and it's source code is available to everyone.
The Linux OS is available open source, and when critical vulnerabilities are found, they are fixed...in minutes or hours, not weeks or months like it takes Microsoft and Apple. Or I guess not at all by Symantec.
There's nothing inherently insecure about source code being publicly available.
The problem is that attackers now have visibility into the poor coding skills ofSymantec and are now able to craft new attacks. Had the source code been available all along, things like this wouldn't really be an issue. Symantec is probably aware of existing vulnerabilities that they didn't take the time to fix, but now might be obvious to a skilled coder. Bad, bad, bad.
Plenty of security software is open source, and available for all to see. See: SSH, OpenSSL, and GPG. OpenSSL powers many many many many web sites (e.g., Google, Amazon, and others). It's what encrypts your credit card data for these sites, and it's source code is available to everyone.
The Linux OS is available open source, and when critical vulnerabilities are found, they are fixed...in minutes or hours, not weeks or months like it takes Microsoft and Apple. Or I guess not at all by Symantec.
When a program is open source, then of course you are right. But when a program is not open source, companies do (as you point out) have fewer incentives to deal with bad code and vulnerabilities so they let things slide.
The open source community would fix things in hours sometimes versus years at non OS organizations.
The problem is that Symantec lost control of its source code in 2006, didn't tell anyone, didn't address the vulnerabilities, and now has egg on its face (to put it mildly).
#7
Original Poster


Join Date: Jan 2010
Location: New York and Vienna
Programs: PA WorldPass Platinum, AA, DL, LH. GHA Black, SPG and HHonors Gold
Posts: 3,872
#8
FlyerTalk Evangelist




Join Date: Sep 2000
Programs: BA, AA, DL, KLM, UA
Posts: 37,489
A source at Symantec (a colleague spoke to someone) confirmed the breach was in 2006 and an article by a colleague of mine reflects that.
Ouch.
#9
Original Poster


Join Date: Jan 2010
Location: New York and Vienna
Programs: PA WorldPass Platinum, AA, DL, LH. GHA Black, SPG and HHonors Gold
Posts: 3,872
Is there an emoticon for "mouth agape"?
#10
Join Date: Oct 2006
Location: IAD, and sometimes OMNI/PR. Currently: not far from IAD, but home will always be SAN (not far from the "touch my junk and I'll have you arrested" Memorial TSA Check Point) even if I'm not there so much these days.
Programs: UA, CO, Calcifer Award for Mad Haiku Skillz
Posts: 5,076
#11
FlyerTalk Evangelist



Join Date: Jun 2005
Posts: 38,543
I strongly disagree.
There's nothing inherently insecure about source code being publicly available.
The problem is that attackers now have visibility into the poor coding skills ofSymantec and are now able to craft new attacks. Had the source code been available all along, things like this wouldn't really be an issue. Symantec is probably aware of existing vulnerabilities that they didn't take the time to fix, but now might be obvious to a skilled coder. Bad, bad, bad.
There's nothing inherently insecure about source code being publicly available.
The problem is that attackers now have visibility into the poor coding skills ofSymantec and are now able to craft new attacks. Had the source code been available all along, things like this wouldn't really be an issue. Symantec is probably aware of existing vulnerabilities that they didn't take the time to fix, but now might be obvious to a skilled coder. Bad, bad, bad.
#12
In Memoriam
Join Date: Feb 2000
Location: Easton, CT, USA
Programs: ua prem exec, Former hilton diamond
Posts: 31,801
In the news again today for new releases
Tue Feb 7, 2012 6:25pm EST
* Code for pcAnywhere published
* Symantec says customers safe
* More releases expected
By Joseph Menn and Frank Jack Daniel
Feb 7 (Reuters) - A hacker released the source code for antivirus firm Symantec's pcAnywhere utility on Tuesday, raising fears that others could find security holes in the product and attempt takeovers of customer computers.
The release followed failed email negotiations over a $50,000 payout to the hacker calling himself YamaTough to destroy the code.
The email thread was published on Monday, but the hacker and the company said their participation had been a ruse. YamaTough said he was always going to publish the code, while Symantec said law enforcement had been directing its side of the talks.
http://www.reuters.com/article/2012/...8D77TN20120207
Tue Feb 7, 2012 6:25pm EST
* Code for pcAnywhere published
* Symantec says customers safe
* More releases expected
By Joseph Menn and Frank Jack Daniel
Feb 7 (Reuters) - A hacker released the source code for antivirus firm Symantec's pcAnywhere utility on Tuesday, raising fears that others could find security holes in the product and attempt takeovers of customer computers.
The release followed failed email negotiations over a $50,000 payout to the hacker calling himself YamaTough to destroy the code.
The email thread was published on Monday, but the hacker and the company said their participation had been a ruse. YamaTough said he was always going to publish the code, while Symantec said law enforcement had been directing its side of the talks.
http://www.reuters.com/article/2012/...8D77TN20120207

