Sun Java System Access Manager Does Not Securely Process XSLT Stylesheets contained in XML Signatures

The Sun Java System Access Manager may not securely process XSLT stylesheets which are contained inside XSLT Transforms in XML Signatures.

A remote user who is able to create such an XML Signature which is viewed locally with Access Manager may be able to execute arbitrary code with the privileges of the Access Manager application. Access Manager is run by a web container application, such as the Sun Java System Application Server, and thus the privileges of Access Manager are the same as the configured web container application.

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

This issue can occur in the following releases:

HP-UX:

• Sun Java System Access Manager 7 2005Q4 without patch 126371-06

Other:

• Sun Java System Access Manager 7.1 WAR file-based installation (all platforms) without patch 140504-01

Note: With respect to Access Manager functionality, this issue only affects verification of XML signing, so if a user is not using XML signing in Access Manager, there is no impact.

To determine if XML signing is enabled for Access Manager, do the following:

1. Login to the Access Manager console
2. Click on the "Configuration" tab for Access Manager 7.x or the "Service Configuration" tab for Access Manager 6.x
3. Select service: "SAML"

If any of the three check boxes labeled "Sign SAML Request", "Sign SAML Response" or "Sign SAML Assertion" is checked, the XML signing functionality is in use.

To determine the version of Access Manager on a Solaris system, the following command can be run:

    % pkginfo -l SUNWamsvc
    PKGINST:  SUNWamsvc
    NAME:  Sun Java System Access Manager Services
    CATEGORY:  application
    ARCH:  all
    VERSION:  7.0,REV=05.08.10.09.17

To determine the version of Sun Java System Access Manager on other systems, the following command can be run (as "root" user):

    # <access-manager-install-dir>/bin/amadmin --version
    Sun Java System Access Manager 7 2005Q4

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

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

This issue is addressed in following releases:

SPARC Platform:

• Sun Java System Access Manager 7.1 (for Solaris 8, 9 and 10) with patch 126356-01 or later
• Sun Java System Access Manager 7 2005Q4 (for Solaris 8, 9 and 10) with patch 120954-06 or later
• Sun Java System Access Manager 6.3 2005Q1 (for Solaris 8, 9 and 10) with patch 119465-12 or later
• Sun Java System Identity Server 6.2 (for Solaris 8 and 9) with patch 115766-15 or later
• Sun Java System Identity Server 6.1 (for Solaris 8 and 9) with patch 117586-22 or later

x86 Platform:

• Sun Java System Access Manager 7.1 (for Solaris 8, 9 and 10) with patch 126357-01 or later
• Sun Java System Access Manager 7 2005Q4 (for Solaris 9 and 10) with patch 120955-06 or later
• Sun Java System Access Manager 6.3 2005Q1 (for Solaris 8, 9 and 10) with patch 119465-12 or later
• Sun Java System Identity Server 6.2 (for Solaris 8 and 9) with patch 120091-15 or later

Linux:

• Sun Java System Access Manager 7.1 with patch 126358-01 or later
• Sun Java System Access Manager 7 2005Q4 with patch 120956-06 or later
• Sun Java System Access Manager 6.3 2005Q1 with patch 119502-12 or later

Windows:

• Sun Java System Access Manager 7.1 with patch 126359-01 or later
• Sun Java System Access Manager 7 2005Q4 with patch 124296-06 or later

HP-UX:

• Sun Java System Access Manager 7 2005Q4 with patch 126371-06 or later

• Sun Java System Access Manager 7.1 WAR file-based installation (all platforms) with patch 140504-01 or later

10-Nov-2008: Updated Contributing Factors and Resolution sections for HP-UX
23-Dec-2008: Add WAR platform and patches to Contributing Factors and Resolution

This solution has no attachment