Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2007.0269 -- [Solaris]
A Security Vulnerability in Sun Cluster Software may Lead to
Data Corruption and "send_mondo" Panics
3 September 2007
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Sun Cluster 3.2
Sun Cluster 3.1
Publisher: Sun Microsystems
Operating System: Solaris
Impact: Denial of Service
Access: Existing Account
Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-26-102874-1
Revision History: September 3 2007: Patches released for Sun Cluster 3.2
April 26 2007: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
Sun(sm) Alert Notification
* Sun Alert ID: 102874
* Synopsis: A Security Vulnerability in Sun Cluster Software may
Lead to Data Corruption and "send_mondo" Panics
* Category: Security
* Product: Sun Cluster 3.1, Solaris Cluster 3.2
* BugIDs: 6497075
* Avoidance: Patch
* State: Resolved
* Date Released: 24-Apr-2007, 31-Aug-2007
* Date Closed: 31-Aug-2007
* Date Modified: 31-Aug-2007
1. Impact
A privileged user on a Sun Cluster node which is a current cluster
member may be able to corrupt in-memory data structures of a sibling
cluster node. This can lead to a system panic and/or data corruption
on the sibling node which can affect application throughput or
availability of data or applications to end users depending on how the
Sun Cluster is configured and is thus a type of Denial of Service
(DoS).
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
* Sun Cluster 3.1 (for Solaris 8) without patch 117950-29
* Sun Cluster 3.1 (for Solaris 9) without patch 117949-29
* Sun Cluster 3.1 (for Solaris 10) without patch 120500-14
* Sun Cluster 3.2 (for Solaris 9) without patch 126105-01
* Sun Cluster 3.2 (for Solaris 10) without patch 126106-01
x86 Platform
* Sun Cluster 3.1 (Solaris 9) without patch 117909-29
* Sun Cluster 3.1 (Solaris 10) without patch 120501-14
* Sun Cluster 3.2 (Solaris 10) without patch 126107-01
Note 1: Sun Cluster 3.0 is not affected by this issue.
Note 2: Sun/Solaris Cluster is not supported on Solaris 8 or Solaris
9 for the x86 platform.
Note 3: The Symcli backup software version 6.2.1 which is supplied by
EMC may trigger this issue and cause attached cluster nodes to panic
or experience data corruption.
Note 4: EMC Symcli backup software is installed under
"/opt/emc/SYMCLI". Under this path, a directory is named as the Symcli
version.
3. Symptoms
If the described issue occurs, data corruption and "send_mondo" panics
may occur with a stack trace similar to the following:
genunix:cdev_ioctl()
did:didioctl()
specfs:spec_ioctl()
pxfs:void fobj_ii::cascaded_ioctl ( )
pxfs:void io_repl_impl::cascaded_ioctl ( )
cl_comm:void _fs_fobj_cascaded_ioctl_receive()
cl_comm:void replica_handler::handle_incoming_call()
cl_comm:void rxdoor::handle_request_common()
cl_comm:void rxdoor::handle_twoway()
cl_comm:void recstream::execute() - frame recycled
cl_comm:void threadpool_worker_t::deferred_task_handler()
cl_comm:void threadpool::thread_handler()
cl_comm:cllwpwrapper()
unix:thread_start()
---xxx---
panic string: send_mondo_set: timeout
Note: A "Bad Trap" panic could be another symptom for this issue.
4. Relief/Workaround
There is no workaround. Please see the Resolution section below.
5. Resolution
This issue is addressed in the following releases:
SPARC Platform
* Sun Cluster 3.1 (for Solaris 8) with patch 117950-29 or later
* Sun Cluster 3.1 (for Solaris 9) with patch 117949-29 or later
* Sun Cluster 3.1 (for Solaris 10) with patch 120500-14 or later
* Sun Cluster 3.2 (for Solaris 9) with patch 126105-01 or later
* Sun Cluster 3.2 (for Solaris 10) with patch 126106-01 or later
x86 Platform
* Sun Cluster 3.1 (Solaris 9) with patch 117909-29 or later
* Sun Cluster 3.1 (Solaris 10) with patch 120501-14 or later
* Sun Cluster 3.2 (Solaris 10) with patch 126107-01 or later
Change History
31-Aug-2007:
* State: Resolved
* Updated Contributing Factors and Resolution sections
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-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 auscert@auscert.org.au
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:
http://www.auscert.org.au/render.html?cid=1980
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:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
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-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQCVAwUBRtt+Eyh9+71yA2DNAQKWvQP/bf52dgUTWP/bjr4bH8PQRFQ402jJcijb
3h/RLQX+5/I/hwpNF/RZgqj2cXYgw1crVOegiT4g31bq9Le21B9M7k+t0mRkqqm5
9F29Y2M6El9ypNc8MqT8NXOF8LvvSEAlSPJM6FrhD96TWv8YJIIpKHpzGcYHvNAy
ijELx/EfN8s=
=MTNO
-----END PGP SIGNATURE-----