Note: This is an archival copy of Security Sun Alert 267088 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1020909.1.
Solaris 8 Operating System
Solaris 9 Operating System
Solaris 10 Operating System
Date of Workaround Release
Multiple Security Vulnerabilities in Solaris TCP (see tcp(7P)) Implementation May Lead to a Denial of Service (DoS) Condition
Multiple security vulnerabilities exist in the Solaris TCP (see tcp(7P)) implementation due to the lack of resource control mechanisms. These issues may allow a remote privileged user with real IP addresses or subnet to easily cause certain network services on the affected system to become unresponsive, which is a type of Denial of Service (DoS). The extent of the impact depends on the network application.
These issues are also referenced in the following documents:
CERT-FI Advisory on the Outpost24 TCP Issues [FICORA #193744] at https://www.cert.fi/haavoittuvuudet/2008/tcp-vulnerabilities.html
CVE CVE-2008-4609 at http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4609
US-CERT VU#723308 at http://www.kb.cert.org/vuls/id/723308
Sun acknowledges with thanks, Jack C. Louis and Robert E. Lee of Outpost24, and CERT-FI for bringing these issues to our attention.
2. Contributing Factors
These issues can occur in the following releases:
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 systems that are not listening to any connections, or which are configured to allow connections only from trusted hosts are
not impacted by these issues.
3. OpenSolaris distributions may include additional bug fixes above and beyond the build from which it was derived. The base build can be derived as follows:-
$ uname -v3. Symptoms
Should the described issues occur, network services on a system may become unresponsive. Services would recover with time once the attack is stopped. If a described issue occurs, Solaris commands such as netstat (see netstat(1M)) may indicate source IP addresses of the attack.
On Solaris 10 and OpenSolaris, ipfilter (see ipfilter(5)) may be used to block connections from source IP addresses of the attacks.
This issue is addressed in the following releases:
Note 1: In addition to the above Resolution, the following new ndd(1M) parameters are available in OpenSolaris, which can be used to limit the usage of memory resources by a given network service.
tcp_listener_limit_conf (read only)
tcp_listener_limit_conf_add (write only)
tcp_listener_limit_conf_del (write only)
Usage is the following.
1. To limit the amount of memory consumed by a web server application on port 80.
# ndd -set /dev/tcp tcp_listener_limit_conf_add 80:<n>where <n> is a number greater than 0.
The above will limit the number of TCP connections the web server can have concurrently such that the maximum amount of memory consumed does not exceed 1/n of the system memory. Note that this is only an approximation.
2. To remove the limit on port 80:
# ndd -set /dev/tcp tcp_listener_limit_conf_del 803. To show the current list of listener limit configurations:
# ndd /dev/tcp tcp_listener_limit_confNote 2: 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.
Copyright 2000-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.
11-Dec-2009: Updated Contributing Factors and Resolution sections for OpenSolaris
19-Jan-2010: Updated Impact section with US-CERT notification
This solution has no attachment