-----BEGIN PGP SIGNED MESSAGE-----
AUSCERT External Security Bulletin Redistribution
ESB-2008.0259 -- [Solaris]
A Security Vulnerability Relating to Inter-Process
Communication (IPC) May Lead to a Denial of Service
13 March 2008
AusCERT Security Bulletin Summary
Publisher: Sun Microsystems
Operating System: Solaris 10
Impact: Denial of Service
Access: Existing Account
- --------------------------BEGIN INCLUDED TEXT--------------------
Solution Type: Sun Alert
Solution 231403 : A Security Vulnerability Relating to
Inter-Process Communication (IPC) May Lead to a Denial of Service
Bug ID: 6642234
Solaris 10 Operating System
Date of Resolved Release: 11-Mar-2008
SA Document Body
A Security Vulnerability Relating to Inter-Process Communication (IPC) May Lead
to a Denial of Service (DoS)
A security vulnerability relating to the Inter-Process Communication
(IPC) message queue sub-system may allow a local unprivileged user to
block all I/O on a message queue until the system is rebooted. This is
a type of Denial of Service (DoS).
2. Contributing Factors
This issue can occur in the following releases:
* Solaris 10 with patch 127111-02 through 127111-09 and
without patch 127111-10
* Solaris 10 with patch 127112-02 through 127112-09 and
without patch 127112-10
Note: Solaris 8 and Solaris 9 are not affected by this issue.
IPC message queue I/O (from the perspective of the application) to one
or more message queues will hang. An attempt to ascertain the state of
the message queue sub-system with the command
$ ipcs -qa
will also hang after the command has output its heading to the screen.
For further confirmation that this issue has occurred, a system panic
could be forced when the above symptom was being exhibited, and the
following command run on the resultant core file:
# echo "::walk thread_cache |::findstack !grep msg_fnd_neg_snd" |mdb -k unix.0 vmcore.
This indicates that the kernel function msg_fnd_neg_snd() was present
on one of the thread stack backtraces which is another symptom that
this issue has likely occurred.
1. Care needs to be taken as to when and how a system panic is
forced; utilities such as 'halt -d', 'reboot -d', or kmdb
'$<systemdump' may be used for this purpose; however, contact your
systems administrator or local support center for advice if you
are in any way unsure about how to proceed with this operation.
2. By default, crash dumps are written to "/var/crash/<hostname>".
See dumpadm(1M) for further information.
There is no workaround for this issue. Please see the Resolution
This issue is addressed in the following releases:
* Solaris 10 with patch 127111-10 or later
* Solaris 10 with patch 127112-10 or later
For more information on Security Sun Alerts, see Technical
Instruction ID 213557.
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-2008 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-----