1. /
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - PGP Universal Server Unauthorized Key Exposure

SYM12-014

August 30, 2012

Revisions

 

None

 

Severity

 

CVSS2

Base Score

Impact

Exploitability

CVSS2 Vector

PGP Key Exposure - Medium

4.14

4.93

5.13

AV:A/AC:L/Au:S/C:P/I:P/A:N 

 

Overview

Symantec’s PGP Universal Server, under specific circumstances, may inadvertently expose a PGP client’s private key.

 

Product(s) Affected

Product

Version

Solution

PGP Universal Server

3.2.x

PGP Universal Server 3.2.1 MP2

 

Details

Symantec became aware that in certain specific instances, the PGP Universal Server failed to properly clear a PGP client’s authenticated session at the termination of an authorized PGP key search request. This could result in the unauthorized exposure of that client’s private key during and immediately following an unauthenticated request from another PGP client. 

Symantec Response

Symantec engineers have verified this issue and released an update addressing it. Symantec recommends customers update to PGP Universal Server 3.2.1 MP2 or later.

 

Update information

Customers may obtain Symantec’s PGP Universal Server 3.2.1 MP2 update through their normal PGP support locations.

Best Practices

As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.
  • Disable remote access if not required or restrict it to trusted/authorized systems only.
  • Where possible, limit exposure of application and web interfaces to trusted/internal networks only.
  • Keep all operating systems and applications updated with the latest vendor patches.
  • Follow a multi-layered approach to security. Run both firewall and anti-malware applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
  • Deploy network and host-based intrusion detection systems to monitor network traffic for signs of anomalous or suspicious activity. This may aid in detection of attacks or malicious activity related to exploitation of latent vulnerabilities

 

Credit

Symantec would like to thank Greg Ose and Mark Gould of CME Group for contacting us concerning this issue and coordinating with us as we resolved it.

 

References

 

BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq ID (BID) to this issue for inclusion in the Security Focus vulnerability database.

CVE: This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. 

 

 

CVE

BID

Description

CVE-2012-3582

BID 55246

PGP Universal Server Unauthorized Key Exposure

 

 

 

Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows responsible disclosure guidelines.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be found at the location below.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Copyright (c) by Symantec Corp.

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com

Disclaimer

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Product Security, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: August 30, 2012
Security Response Blog
The State of Spam