-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2012.0834
          Security Advisories Relating to Symantec Products - PGP
                Universal Server Unauthorized Key Exposure
                             3 September 2012

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           PGP Universal Server
Publisher:         Symantec
Operating System:  Linux variants
Impact/Access:     Access Confidential Data -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2012-3582  

Original Bulletin: 
   http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=2012&suid=20120830_00

- --------------------------BEGIN INCLUDED TEXT--------------------

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

Symantecs PGP Universal Server, under specific circumstances, may inadvertently 
expose a PGP clients 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 clients authenticated session at the 
termination of an authorized PGP key search request. This could result in the 
unauthorized exposure of that clients 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 Symantecs 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

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        http://www.auscert.org.au/render.html?cid=1980

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBUEQ7ue4yVqjM2NGpAQK2iA/+OHvbgYmB4ApXXjFqzwAQKr0uS72otx6d
fFkyT4k7IiNdeZAqPIeut1TzS/IQpJeYLLcj+R/V67RLNPbZYQ0idh+ltNAcIiQT
fG90Mk3pe1C5HU6hwZNAn32aKuoi0Zk0LR94Ig9RcpCqhgIO6XBEfmHlwIXfpCPW
xC3wsH48cBl+g0IgldBgKxTxJEW2QNel5AVf3tgRi6WR2h7tFGhE2MAxQ+hBycWs
t/1Tx20/dfGfriIEVZ9/rt4E7I9/6TGSjI+OVDMmWUcbeLpcc9iYKeRifFdYSURT
T0mXEOvqFQdg5ZqmY/MRK5oV+zUPcmoaL/go/PjLa29+iZgJMWDhHWf2wHlEqXOs
NLfAkyxntcm1EpKgQ2vyRXcDpFu7l51ve5V4UN8n8EdHyvTNWIswmnA61VfuuF+e
Z891OdNS/aPiDcDFIK+i07ZlIMdQPpuoBPx8wJPjc7LRuf7NwJbJqLs9ks99bsvq
bLqIyBomfnuKTqeA9WhfDfiNQRKaXSCacDGT+6977wFapFcY2eyKa9K0Oi6tuxSL
/dc57Ta3ePbwew1re4TEG5ku1vYYLclNAXvldrhFM7AfyLDVRVrK5MpPzSvSPENI
kDlF2h2s8rAomLFxolvX8DEK+AHPEaw21peLXMW6WrSAmtek2GKaf558B4TE7OBi
zz7NdDitbw4=
=2i2+
-----END PGP SIGNATURE-----