Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =========================================================================== AUSCERT External Security Bulletin Redistribution ESB-2008.0573 -- [Solaris] Small Appending Writes May Result in Data Loss in Sun/Solaris Cluster 3.1 or 3.2 Filesystem 3 June 2008 =========================================================================== AusCERT Security Bulletin Summary --------------------------------- Product: Solaris Cluster 3.2 Sun Cluster 3.1 Publisher: Sun Microsystems Operating System: Solaris Impact: Modify Arbitrary Files Access: Existing Account Ref: ESB-2007.0269 Original Bulletin: http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-200200-1 - --------------------------BEGIN INCLUDED TEXT-------------------- Solution Type: Sun Alert Solution 200200 : Small Appending Writes May Result in Data Loss in Sun/Solaris Cluster 3.1 or 3.2 Filesystem Previously Published As: 102778 Product Sun Cluster 3.1 Solaris Cluster 3.2 Bug ID: 6507810 Date of Workaround Release: 18-JAN-2007 Date of Resolved Release: 29-May-2008 SA Document Body Small Appending Writes May Result in Data Loss in Sun/Solaris Cluster 3.1 or 3.2 Filesystem 1. Impact In rare cases, small appending writes to a file located on a Sun Cluster 3.1 or Solaris Cluster 3.2 filesystem may result in some data that was written to be lost and replaced with random data. 2. Contributing Factors This issue can occur in the following releases: SPARC Platform * Sun Cluster 3.1 (for Solaris 8) with patch 117950-25 through 117950-28 and without patch 117950-29 * Sun Cluster 3.1 (for Solaris 9) with patch 117949-25 through 117949-28 and without patch 117949-29 * Sun Cluster 3.1 (for Solaris 10) with patch 120500-10 through 120500-13 and without patch 120500-14 * Solaris Cluster 3.2 (for Solaris 9) without patch 125510-01 * Solaris Cluster 3.2 (for Solaris 10) without patch 125511-01 x86 Platform * Sun Cluster 3.1 (for Solaris 9) with patch 117909-25 through 117909-28 and without patch 117909-29 * Sun Cluster 3.1 (for Solaris 10) with patch 120501-10 through 120501-13 and without patch 120501-14 * Solaris Cluster 3.2 (for Solaris 10) without patch 125512-01 Notes: 1. Sun Cluster 3.0 is not affected by this issue. 2. Sun/Solaris Cluster is not supported for Solaris 8 on the x86 platform. 3. Solaris Cluster 3.2 is not supported for Solaris 9 on the x86 platform. 3. Symptoms Should the described issue occur, the file being written to will contain a section of random data or null bytes instead of the expected data. The file will usually contain valid data before and after the corrupted data. 4. Workaround To work around this issue, the affected patches may be removed to return to a safe revision of the patch. Remove the latest cluster core patch (117950, 117949, 117909) and re-install version -11 or earlier. (Note this older revision is required due to similar issues also being reported in Sun Alert 102333. There is no safe revision for Solaris 10). Note: If "scinstall" was used to install or upgrade to Sun Cluster 3.1_U4 you will not be able to remove the core patch. Or, the following work around may be applied: 1. Add the following entry to the "/etc/system" file on all nodes of the cluster: set pxfs:pxfs_software_mount_level=1 2. Shut down the entire cluster: $ scshutdown -y -g0 3. Wait for all nodes in the cluster to be down. 4. Restart all nodes in the cluster. Note: This workaround may impact performance for Sun Cluster file systems. 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 * Solaris Cluster 3.2 (for Solaris 9) with patch 125510-01 or later * Solaris Cluster 3.2 (for Solaris 10) with patch 125511-01 or later x86 Platform * Sun Cluster 3.1 (for Solaris 9) with patch 117909-29 or later * Sun Cluster 3.1 (for Solaris 10) with patch 120501-14 or later * Solaris Cluster 3.2 (for Solaris 10) with patch 125512-01 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 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-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 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 iQCVAwUBSESOOSh9+71yA2DNAQKO6AP+NB3ExyYyFi+qPbRE+DWAbG5usRzVrHIf mZ+HZHMYIHdfxgDQZEH5JrExRBqZG3iKV9dkibgfgVGEr3+6QfFfg29/ThKiIjCB c5NNpU7ZLDQOZwHR0zDTFzvEJJhyvot6VaAA0zj6HZbhzTYq05NUO5h8R97SkRJP jtEFiGZkjpE= =/nBI -----END PGP SIGNATURE-----