Bug Id
6710920

Product
Solaris 8 Operating System
Solaris 9 Operating System

Date of Workaround Release
14-Nov-2008

Date of Resolved Release
22-May-2009

A Buffer Overflow Security Vulnerability in the Solaris sadmind(1M) Daemon May Lead to Execution of Arbitrary Code

1. Impact

A buffer overflow security vulnerability in the Solaris sadmind(1M) daemon may allow a local or remote unprivileged user to execute arbitrary code with root privileges.

Sun acknowledges with thanks, Adriano Lima of RISE security for bringing this issue to our attention.

This issue is described in the following documents:


2. Contributing Factors

This issue can occur in the following releases:

SPARC Platform

• Solaris 8 without patch 116455-02
• Solaris 9 without patch 116453-03

x86 Platform

• Solaris 8 without patch 116442-02
• Solaris 9 without patch 116454-03

Notes:

1. Solaris 8 entered EOSL Phase 2 on 1 April 2009. Entitlement to patches developed on or after 1 April 2009 requires the purchase of the Solaris 8 Vintage Patch Service. See note in section 5 for more details.

2. Solaris 10 and OpenSolaris do not ship with sadmind(1M) and therefore are not affected by this issue.

To determine if sadmind(1M) is enabled on the system, the following command can be run:

$ grep sadmind /etc/inet/inetd.conf
100232/10  tli  rpc/udp wait root /usr/sbin/sadmind  sadmind

3. Symptoms

There are no predictable symptoms that would indicate this issue has been exploited to execute arbitrary code.

4. Workaround

To work around this issue, sadmind(1M) can be disabled by doing the following:

1. Edit the '/etc/inetd.conf' file as the root user to comment out the entry for sadmind(1M). This entry will then read as:

#100232/10   tli   rpc/udp wait root /usr/sbin/sadmind    sadmind

2. Restart the inetd(1M) process to reread the newly modified '/etc/inetd.conf' file. This may be done using the following command:

# /usr/bin/pkill -HUP inetd

5. Resolution

This issue is addressed in the following releases:

SPARC Platform

• Solaris 8 with patch 116455-02 or later
  
• Solaris 9 with patch 116453-03 or later

x86 Platform

• Solaris 8 with patch 116442-02 or later
• Solaris 9 with patch 116454-03 or later

Note: The READMEs of Solaris 8 patches developed on or after 1 April 2009 are available to all customers. However, Solaris 8 entered EOSL Phase 2 on April 1, 2009 and thus entitlement for these patches, including those that fix security vulnerabilities, requires the purchase of the Solaris 8 Vintage Patch Service. More information about the Solaris 8 Vintage Patch Service is available at:


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.

Modification History
09-Jan-2009: Updated Workaround section for IDRs
22-May-2009: Updated Contributing Factors and Resolution sections, Resolved

References

116455-02
116453-03
116442-02
116454-03





Attachments

This solution has no attachment