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

A Security Vulnerability Exists if an OpenSolaris System was Joined to a Windows Domain Using kclient(1M) or smbadm(1M)



Category
Security

Release Phase
Resolved

Bug Id
6913788, 6913833

Product
OpenSolaris

Date of Resolved Release
26-Jan-2010

A Security Vulnerability Exists if an OpenSolaris System was Joined to a Windows Domain Using kclient(1M) or smbadm(1M)

1. Impact

An insecure default configuration security vulnerability exists in the way the Kerberos client utility (kclient(1M)) and the CIFS configuration utility (smbadm(1M)) join a Windows Active Directory domain.

2. Contributing Factors

This issue can occur in the following releases:

SPARC Platform
  • OpenSolaris based upon builds snv_77 through snv_131 for smbadm(1M)
  • OpenSolaris based upon builds snv_91 through snv_131 for kclient(1M)
x86 Platform
  • OpenSolaris based upon builds snv_77 through snv_131 for smbadm(1M)
  • OpenSolaris based upon builds snv_91 through snv_131 for kclient(1M)
Note: Solaris 8, 9, and 10 are not impacted by this issue.

OpenSolaris distributions may include additional bug fixes above and beyond the build from which it was derived. To determine the base build of OpenSolaris, the following command can be used:
$ uname -v
snv_131

3. Symptoms

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

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
  • OpenSolaris based upon builds snv_132 or later for smbadm(1M) and kclient(1M)
x86 Platform
  • OpenSolaris based upon builds snv_132 or later for smbadm(1M) and kclient(1M)
Note: kclient(1M) or smbadm(1M) must be rerun on the client after updating to snv_132 or later in order to generate sufficiently random password/keys for the computer account in Windows Active Directory.

For kclient(1M), an example would be:
$ kclient -T ms_ad
For smbadm(1M), an example would be:
$ smbadm join -u administrator EXAMPLE.COM
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-2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.











Attachments
This solution has no attachment