WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
April 5, 2007
Symantec Enterprise Security Manager Remote Upgrade Authentication Bypass

Revision History
Added note clarifying that ESM 6.5.3 is not vulnerable.


Local AccessYes
Authentication RequiredNo
Exploit publicly availableNo

Symantec Enterprise Security Manager is susceptible to a remote code execution vulnerability.

Vulnerable Products
The following supported ESM agent and manager platforms have patches available for immediate download. While the ESM manager is not vulnerable, it must be updated to work with the new agents.

Note: ESM 6.5.3 already includes the fixes and is not vulnerable.

ESM agent platformESM version
AIX (4.3.1, 4.3.3, 5.1, 5.2)
AIX (5.1, 5.2)
AIX 5L 5.1 (32-bit tested on 64-bit)
AIX 5L 5.2 (32-bit tested on 32-bit)
AIX 5L 5.3 (64-bit)
HP Tru64/OSF-1 4.0D - 5.1A (Digital Unix)
HP-UX (10.20, 11.0, 11i) (PA-RISC)
HP-UX (11.0, 11.11i) (PA-RISC)
HP-UX 10.20 (PA-RISC)
HP-UX 11i v2 (Itanium)
NCR UNIX 3.2 (ESM 5.1 only w/SU7b updated in 2003)
Red Hat Enterprise Linux (ES 2.1)
Red Hat Enterprise Linux 4 AS (Xeon and Opteron)
Red Hat Enterprise Linux 4 ES (x86)
Red Hat Enterprise Linux ES 2.1 (x86)
Red Hat Enterprise Linux ES 3.0 (x86)
Red Hat Enterprise Linux ES 3.0 (x86)
Red Hat Enterprise Linux ES 4.0 Itanium
Red Hat Linux 8
Red Hat Linux 9
Red Hat Linux AS 3.0 64-bit (Itanium)
Red Hat Linux AS 3.0 64-bit (Opteron and Xeon)
Red Hat Linux WS 3.0 64-bit (Opteron and Xeon)
SUSE Linux Enterprise Server 8 (x86)
SUSE Linux Enterprise Server 9 (Itanium)
SUSE Linux Enterprise Server 9 (x86)
SUSE Linux Standard Server 8 (x86)
Solaris 2.10 (SPARC)
Solaris 2.10 (x86)
Solaris 2.6 (SPARC)
Solaris 2.9 (SPARC)
Solaris 2.9 (SPARC)
Windows 2000 (Professional, Server, Advanced Server)
Windows 2000 Advanced Server w/SP1+ (x86)
Windows 2000 Professional w/SP1+ (x86)
Windows 2000 Server w/ SP1+ (x86)
Windows NT 4.0
Windows NT 4.0 Workstation w/SP6a+
Windows NT 4.0 Server w/SP6a+
Windows Server 2003 (Itanium)
Windows Server 2003 (x86) (no SP)
Windows Server 2003 Enterprise Edition SP1 (x86)
Windows Server 2003 Standard Edition SP1 (x86)
Windows XP Professional w/SP1 (x86)
Windows XP Professional (x86) (no SP)
Windows XP Professional SP2 (x86)
All versions prior to 6.5.3

ESM manager platformESM version
AIX 4.2.1
AIX 4.3.1, 4.3.3
AIX 4.3.3
AIX 5L 5.1
AIX 5L 5.2
HP-UX (10.20, 11.0, and 11.11) (PA-RISC)
HP-UX 10.20 (PA-RISC)
HP-UX 11.0 (PA-RISC)
HP-UX 11.23 (PA-RISC)
HP-UX 11i v1 (11.11) (PA-RISC)
Solaris 2.51 (SPARC)
Solaris 2.6 (SPARC)
Solaris 2.7 (SPARC)
Solaris 2.8 (SPARC)
Solaris 2.9 (SPARC)
Windows 2000 Advanced Server SP1+
Windows 2000 Advanced Server SP4+
Windows 2000 Professional SP1+
Windows 2000 Professional SP4+
Windows 2000 Server SP1+
Windows 2000 Server SP4+
Windows NT 4.0 Server w/SP6a+
Windows NT 4.0 Workstation w/SP6a+
Windows Server 2003
All version prior to 6.5.3

The following ESM Agents are not affected because they do not support remote upgrade.

ESM agent platformESM version
NetWare 6.0
NetWare 6.5
OS/400 V5R2
OS/400 V5R3
OpenVMS AXP 7.2
OpenVMS AXP 7.3

All versions of the Enterprise Security Manager (ESM) are vulnerable to a remote code execution attack. The vulnerability exists in the ESM agent remote upgrade interface. The ESM agent accepts remote upgrade requests from any entity that understands the upgrade protocol. The ESM agent does not currently verify that upgrades are from a trusted source. An attacker with knowledge of the agent protocol could deploy a piece of software that allows the attacker to control the host computer. The ESM agent runs with administrative privileges.

Symantec Response
Symantec has released downloadable automated and manual fixes for all supported ESM agents.

To date, Symantec is not aware of any reported attempts to exploit this vulnerability.

For more information about installing or updating ESM components see the Symantec Enterprise Security Manager Installation Guide.

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 the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).

Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A Symantec Product Security team member will contact you regarding your submission. 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 end of this message.

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.

PDF Symantec Vulnerability Response Policy PGP Symantec Product Vulnerability Management PGP Key

Copyright © 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 Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.

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 Security Response, 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.

Initial Post on: Thursday, 05-Apr-07 14:25:00
Last modified on: Friday, 06-Apr-07 09:00:34