Note: This is an archival copy of Security Sun Alert 270809 as previously published on http://sunsolve.sun.com.
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1021101.1.
Article ID : 1021101.1
Article Type : Sun Alerts (SURE)
Last reviewed : 2009-10-28
Audience : PUBLIC
Copyright Notice: Copyright © 2010, Oracle Corporation and/or its affiliates.

Security Vulnerability in Solaris Trusted Extensions may Prevent XScreenSaver (xscreensaver(1)) From Running



Category
Security

Release Phase
Resolved

Bug Id
6865652

Product
Solaris 10 Operating System

Date of Resolved Release
29-Oct-2009

A security vulnerability in Solaris Trusted Extensions may result in a condition that prevents XScreenSaver (xscreensaver(1)) from running:

1. Impact

A security vulnerability in Solaris Trusted Extensions may result in a condition that prevents XScreenSaver (xscreensaver(1)) from running. The screen may not lock if a user chooses to lock the screen from the JDS menu or if the screen is left unattended. This condition occurs when trying to restart XScreenSaver using "xscreensaver-demo".

2. Contributing Factors

This issue can occur in the following releases:

SPARC Platform
  • Solaris 10 with patch 125533-14 or later and without patch 120094-28
x86 Platform
  • Solaris 10 with patch 125534-14 or later and without patch 120095-28
Note 1:  Solaris 8, Solaris 9, and OpenSolaris are not impacted by this issue.

Note 2:  This issue only impacts Solaris 10 systems that have installed and configured Solaris Trusted Extensions.

To determine if a system is configured with Trusted Extensions, the following command can be run:
    $ svcs /system/labeld
STATE STIME FMRI
online 07:08:09 svc:/system/labeld:default
If the state is disabled or if "/system/labeld" service is not listed, then the system is not configured to use Trusted Extensions.

Note 3:  This issue only occurs when a user is logged into JDS.

3. Symptoms

If the described issue occurs, the XScreenSaver (xscreensaver(1)) process will not be running. This can be determined by running the following command:
   $ /usr/openwin/bin/xscreensaver-command -version
If the above command reports:
    no screensaver is running on display <hostname>:NN.N
then the XScreenSaver (xscreensaver(1)) process is not running.

4. Workaround

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

5. Resolution

This issue is addressed in the following releases:

SPARC Platform
  • Solaris 10 with patch 120094-28 or later
x86 Platform
  • Solaris 10 with patch 120095-28 or later
For more information on Security Sun Alerts, see 1009886.1.

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-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


References

120094-28
120095-28





Attachments
This solution has no attachment