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

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

                    ESB-2007.0521 -- [Win][UNIX/Linux]
          Java Runtime Environment Does Not Securely Process XSLT
                  Stylesheets Contained in XML Signatures
                               12 July 2007

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

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

Product:              Java 2 Platform, Standard Edition
Publisher:            Sun Microsystems
Operating System:     Windows
                      UNIX variants (UNIX, Linux, OSX)
Impact:               Execute Arbitrary Code/Commands
Access:               Existing Account

Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-26-102993-1

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

Sun(sm) Alert Notification
     * Sun Alert ID: 102993
     * Synopsis: Java Runtime Environment Does Not Securely Process XSLT
       Stylesheets Contained in XML Signatures
     * Category: Security
     * Product: Java 2 Platform, Standard Edition
     * BugIDs: 6519471
     * Avoidance: Patch, Upgrade
     * State: Resolved
     * Date Released: 10-Jul-2007
     * Date Closed: 10-Jul-2007
     * Date Modified: 

1. Impact

   The Java XML Digital Signature implementation that is included in the
   JDK and JRE 6 release does not securely process XSLT stylesheets
   contained in XSLT Transforms in XML Signatures. This could lead to the
   execution of arbitrary code with the permissions of the application
   processing XML signatures that include these XSLT stylesheets.

   Sun acknowledges with thanks, Brad Hill of iSEC Partners, for bringing
   this issue to our attention.

2. Contributing Factors

   This issue can occur in the following releases (for Windows, Solaris,
   and Linux):
     * JDK and JRE 6 Update 1 and earlier

   Note: SDK and JRE 5.0 and 1.4.x are not affected by this issue. (The
   XML Digital Signature implementation was not included in SDK and JRE
   5.0 and 1.4.x releases).

   For this vulnerability to be exploited, a trusted application needs to
   process an XML signature with an XSLT stylesheet that contains
   malicious content. This vulnerability cannot be exploited through an
   untrusted applet or untrusted Java Web Start application.

   To determine the default version of the JRE on a system for Solaris
   and Linux, the following command can be run:
    % java -version

   (The above command only determines the default version. Other versions
   may also be installed on the system).

   To determine the default version of the JRE on a system for Windows:
    1. Click "Start"
    2. Select "Run"
    3. Type "cmd" (starts a command-line)
    4. At the prompt, type "java -version"

   (The above command only determines the default version. Other versions
   may also be installed on the system).

3. Symptoms

   There are no predictable symptoms that would indicate the described
   issue has been exploited. 

4. Relief/Workaround

   There is no workaround for this issue. Please see the Resolution
   section below.

5. Resolution

   This issue is addressed in the following releases (for Windows,
   Solaris, and Linux):
     * JDK and JRE 6 Update 2 or later

   Java SE 6 is available for download at the following link:

   http://java.sun.com/javase/downloads/index.jsp

   Java SE 6 Update 2 for Solaris is available in the following patches:
     * Java SE 6 update 2 (as delivered in patch 125136-02 or later)
     * Java SE 6 update 2 (as delivered in patch 125137-02 or later
       (64bit))
     * Java SE 6_x86 update 2 (as delivered in patch 125138-02 or
       later)
     * Java SE 6_x86 update 2 (as delivered in patch 125139-02 or
       later (64bit))

   Note: When installing a new version of the product from a source other
   than a Solaris patch, it is recommended that the old affected versions
   be removed from your system. For more information, please see the
   installation notes on the respective java.sun.com download pages.

   This Sun Alert notification is being provided to you on an "AS IS"
   basis. This Sun Alert notification may contain information provided by
   third parties. The issues described in this Sun Alert notification may
   or may not impact your system(s). Sun makes no representations,
   warranties, or guarantees as to the information contained herein. ANY
   AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
   WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
   NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT
   YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
   INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE
   OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN.
   This Sun Alert notification contains Sun proprietary and confidential
   information. It is being provided to you pursuant to the provisions of
   your agreement to purchase services from Sun, or, if you do not have
   such an agreement, the Sun.com Terms of Use. This Sun Alert
   notification may only be used for the purposes contemplated by these
   agreements.

   Copyright 2000-2006 Sun Microsystems, Inc., 4150 Network Circle, Santa
   Clara, CA 95054 U.S.A. All rights reserved

- --------------------------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

If you believe that your computer system has been compromised or attacked in 
any way, we encourage you to let us know by completing the secure National IT 
Incident Reporting Form at:

        http://www.auscert.org.au/render.html?it=3192

===========================================================================
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

iQCVAwUBRpWLqyh9+71yA2DNAQLDaAQAkU884E+6S0cayzhgf5jdYi0GaaCxnHS0
XYBYZPKeIP5pKA+1O59oUogeV2nHu1w2aEMcHsfpm4DBlTrgsI7g35iK25VoO7gK
TbYKHCpsKDf18dlShBDbh5m3tZm/l9nLy32wS17QFdK2EtccvMUZqELJZMBCsun7
xBNy9aKpbC0=
=4bZS
-----END PGP SIGNATURE-----