WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
January 4, 2005
Sun Alert ID 57591: Java Runtime Environment (JRE)

Revision History

Risk Impact

As a result of a reported vulnerability in the Java Runtime Environment (JRE) in Sun Alert ID 57591, Symantec is issuing hotfixes for affected Symantec Security Gateway and Firewall products.

Affected Components
Symantec Gateway Security 5400 Series v2.0.1
Symantec Gateway Security 5400 Series v2.0
Symantec Enterprise Firewall v8.0

The JRE is used to manage the security gateway. No risk is posed to the security gateway itself, however, the client machines used to manage the gateway may be exposed through the console. Upon initial connection, the security gateway installs the JRE onto a system if the appropriate JRE is not already installed on the client. Currently, this is a version of the JRE that has been determined to be vulnerable. The hotfix updates the JRE included on the security gateway to the latest non-vulnerable JRE from Sun Microsystems, 1.4.2_06.
Symantec recommends customers update the management systems with the latest non-vulnerable JRE from Sun Microsystems. Customers who have already installed the latest non-vulnerable JRE from Sun Microsystems on management systems do not need to take further action at the management station.

Symantec Response
Symantec has released a hotfix to address this issue. Symantec strongly recommends customers apply the appropriate hotfix for their affected product models/versions immediately to protect against this type of threat. Product specific hotfixes are available via the Symantec Enterprise Support site http://www.symantec.com/techsupp.

Symantec is not aware of any active attempts against or organizations impacted by this issue.

The Common Vulnerabilities and Exposures (CVE) initiative has assigned Candidate CAN-2004-1029 to the original Sun JRE issue.
This is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.

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.

Last modified on: Wednesday, 05-Jan-2005 09:01:03 PST