Perimeter
Guest Blog // Selected Security Content Provided By Sophos
What's This?
1/7/2013
08:55 AM
Dark Reading
Dark Reading
Security Insights
Connect Directly
RSS
E-Mail
50%
50%

Another Zero-Day For Symantec PGP WDE

Symantec PGP Desktop is having a bumpy new year with a second zero-day vulnerability released in 13 days. Take action to protect your data

Thirteen days ago on Dec. 25, a security researcher named Nikita Tarakanov uncovered an arbitrary memory overwrite vulnerability in Symantec's PGP Desktop Whole Disk Encryption solution, according to this pastebin note. The pgpwded.sys version 10.2.0.2599 kernel driver distributed with Symantec PGP Desktop 10.2.0 Build 2599 (up to date) is vulnerable to malicious code execution in the handling of IOCTL 0x80022058.

Local access to the device is required in order to successfully exploit the vulnerability. Keeping that in mind, Symantec's response to Nikita via this blog posting states, "It's not of big concern as the stars need to be aligned for this to be exploited."

Nikita has been hard at work with a response to Symantec's blog posting and today unveiled an integer overflow vulnerability in the handling of IOCTL 0x80022094 within the pgpwded.sys kernel. You can read through the details in this pastebin note.

Once again, exploiting this new vulnerability is possible with arbitrary code execution, but requires local execution.

In the Twittersphere, Nikita has a tone of taunting dislike for Symantec with these tweets:

Nikita Tarakanov ‏@NTarakanov
This #0day affects all versions of Windows! Aligner of stars is counter-striking! :D

Nikita Tarakanov ‏@NTarakanov
Dirty PoC for Second #0day in Symantec PGP Desktop http://pastebin.com/W2VUMBJk You have to be able to align stars to exploit it! ;D

Nikita Tarakanov ‏@NTarakanov
Such lame vulns show: there is NO quality assurance in Symantec! #sad_but_true

Since it's still early in the morning at the time of this posting, there has been no response from Symantec yet. I can hardly blame the company, though: My gut tells me this has become personal and is not over yet. Symantec will need to choose its words more carefully to no longer feed the fire named Nikita.

Until Symantec releases a patch in February for the first vulnerability, the best way to protect your data in the meantime is to make sure you have PGP Desktop's Pre-Boot Authentication (PBA) enabled so that Windows doesn't load until after user authentication. In the event PBA is not enabled, make sure it becomes enabled today, and hope you don't lose any encrypted laptops with Symantec's PGP Desktop 10.2.0 Build 2599.

No security, no privacy. Know security, know privacy.

David Schwartzberg is a Senior Security Engineer at Sophos, where he specializes in the latest trends in malware, Web threats, endpoint and data protection, mobile security, and cloud and network security. He is a regular speaker at security conferences and serves as a guest blogger for the award winning Naked Security blog. David talks regularly with technology executives and professionals to help protect their organizations against the latest security threats. Follow him on Twitter @DSchwartzberg

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.