Date: 21 January 2009
References: AU-2009.0007 AU-2009.0005
Click here for printable version
Click here for PGP verifiable version
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2008.0892 -- [Solaris]
Security Vulnerability in the ACL (acl(2)) Implementation for UFS File
Systems May Allow a Local User to Panic the System
22 January 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: acl
Publisher: Sun Microsystems
Operating System: Solaris
Impact: Denial of Service
Access: Existing Account
CVE Names: CVE-2008-4160
Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-242267-1
Revision History: January 22 2009: Added patches for Solaris 8
January 16 2009: Added patches for Solaris 9 and 10
October 16 2008: Updated Resolution
September 29 2008: Added CVE information
September 22 2008: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
Solution Type: Sun Alert
Solution 242267 : Security Vulnerability in the ACL (acl(2))
Implementation for UFS File Systems May Allow a Local User to Panic
the System
Bug ID: 6748275
Product
Solaris 8 Operating System
Solaris 9 Operating System
Solaris 10 Operating System
OpenSolaris
Date of Preliminary Release: 18-Sep-2008
Date of Workaround Release: 15-Jan-2009
Date of Resolved Release: 21-Jan-2009
SA Document Body
Security Vulnerability in the ACL (acl(2)) Implementation for UFS File
Systems May Allow a Local User to Panic the System
1. Impact
A security vulnerability in the Solaris Access Control List (ACL) (see
acl(2)) implementation for UFS file systems may allow a local
unprivileged user to panic a system which has a UFS filesystem. This
is a type of Denial of Service (DoS).
Sun would like to acknowledge with thanks, Nils Goroll, for bringing
this issue to our attention and aiding us in the development of a fix
through the OpenSolaris project.
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
* Solaris 8 without patch 117350-60
* Solaris 9 without patch 122300-34
* Solaris 10 without patch 139483-01
* OpenSolaris based upon builds snv_01 through snv_99
x86 Platform
* Solaris 8 without patch 117351-60
* Solaris 9 without patch 122301-34
* Solaris 10 without patch 139484-01
* OpenSolaris based upon builds snv_01 through snv_99
Note: This issue only affects systems which have UFS file systems
mounted which are writable (read-write). To print the list of UFS file
systems mounted read-write on the system, the following command can be
run:
$ mount -p | grep ufs | grep rw
3. Symptoms
If this issue is experienced, the system will panic with a message
similar to the following:
panic[cpu0]/thread=300043e8060: BAD TRAP: type=31 rp=2a10165f130 addr=70 mmu_fs
r=0
occurred in module "ufs" due to a NULL pointer dereference
unix:die+78 (...)
unix:trap+9e0 (...)
unix:ktl0+48 (...)
ufs:ufs_acl_access+4 (...)
ufs:ufs_dirlook+48 (...)
ufs:ufs_lookup+2ac (...)
genunix:fop_lookup+28 (...)
genunix:lookuppnvp+344 (...)
genunix:lookuppnat+120 (...)
genunix:lookupnameat+5c (...)
genunix:cstatat_getvp+198 (...)
genunix:cstatat64_32+40 (...)
Note that either ufs_acl_access() or ufs_iaccess() are the top most
UFS functions in the call stack.
4. Workaround
There is no workaround for this issue. Please see the Resolution
section below.
5. Resolution
This issue is addressed in the following releases:
SPARC Platform
* Solaris 8 with patch 117350-60 or later
* Solaris 9 with patch 122300-34 or later
* Solaris 10 with patch 139483-01 or later
* OpenSolaris based upon builds snv_100 or later
x86 Platform
* Solaris 8 with patch 117351-60 or later
* Solaris 9 with patch 122301-34 or later
* Solaris 10 with patch 139484-01 or later
* OpenSolaris based upon builds snv_100 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
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-2009 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
iQCVAwUBSXf9jCh9+71yA2DNAQK/IAP9Eb2Y8cpXHxoH4NDlfiri6d3JRpZFtJ5+
2qiEpxsDEntd3SM/itgSGlXebiWwKD1YhXwePd4BFQAyAKx48FfjJm61Z8QTumHg
7tgLBYFyrUff6AF45snuxPIJ4u0yYTTGKD11CF59Xxb8ZVKp8e0Yw+dfAhr40t/0
Ktm2/LTXvZ0=
=ugkh
-----END PGP SIGNATURE-----
|