-----BEGIN PGP SIGNED MESSAGE-----
AUSCERT External Security Bulletin Redistribution
ESB-2006.0491 -- [Solaris]
Security Vulnerabilities in The Solaris Event Port API May
Result in a Denial of Service (DoS) Condition
24 July 2006
AusCERT Security Bulletin Summary
Product: Solaris 10
Publisher: Sun Microsystems
Operating System: Solaris 10
Impact: Denial of Service
Access: Existing Account
- --------------------------BEGIN INCLUDED TEXT--------------------
Sun(sm) Alert Notification
* Sun Alert ID: 102485
* Synopsis: Security Vulnerabilities in The Solaris Event Port API
May Result in a Denial of Service (DoS) Condition
* Category: Security
* Product: Solaris 10 Operating System
* BugIDs: 6367349, 6358194, 6357796, 6362390
* Avoidance: Patch
* State: Resolved
* Date Released: 19-Jul-2006
* Date Closed: 19-Jul-2006
* Date Modified:
Security vulnerabilities in the Solaris event port API may allow a
local unprivileged user the ability to run an application which uses
the API in such a way as to cause the system to panic, leading to a
Denial of Service (DoS) condition.
The Apache server is an example of an application that makes use of
the event port API. On a system running Apache2 (Apache/2.2.0) it may
be possible for a remote unprivileged user to cause that system to
panic, resulting in a Denial of Service (DoS) condition.
2. Contributing Factors
This issue can occur in the following releases:
* Solaris 10 without patch 118833-12
* Solaris 10 without patch 118855-10
Note 1: Solaris 8 and Solaris 9 are not affected by this issue.
Note 2: The Apache 2 web server that is distributed with Solaris 10 in
packages SUNWapch2d and SUNWapch2u is not affected by this issue.
To determine if apache is using event port API, the following command
can be used:
# pfiles <httpd pid> | grep S_IFPORT
14: S_IFPORT mode:0000 dev:301,0 uid:1 gid:12 size:0
Note: <httpd pid> refers to the process id of the apache process.
The above example indicates that the apache process has create an
event port, hence this version of apache is vulnerable.
The above command will produce no output on an unaffected system.
If the described issue occurs, the system will panic with a panic
stack trace similar to one of the following:
There is no workaround. Please see the "Resolution" section below.
This issue is addressed in the following releases:
* Solaris 10 with patch 118833-12 or later
* Solaris 10 with patch 118855-10 or later
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
notification may only be used for the purposes contemplated by these
Copyright 2000-2006 Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reserved
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to email@example.com
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
Australian Computer Emergency Response Team
The University of Queensland
Internet Email: firstname.lastname@example.org
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----