Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2007.0292 -- [Solaris]
Solaris 9 Systems With Solaris Auditing (BSM) Enabled may
Panic if Certain Audit Classes are Being Audited
3 May 2007
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Solaris 9 Operating System
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-102900-1
- --------------------------BEGIN INCLUDED TEXT--------------------
Sun(sm) Alert Notification
* Sun Alert ID: 102900
* Synopsis: Solaris 9 Systems With Solaris Auditing (BSM) Enabled
may Panic if Certain Audit Classes are Being Audited
* Category: Security, Availability
* Product: Solaris 9 Operating System
* BugIDs: 4714273
* Avoidance: Patch, Workaround
* State: Resolved
* Date Released: 01-May-2007
* Date Closed: 01-May-2007
* Date Modified:
1. Impact
Local unprivileged users may be able to panic Solaris systems which
have Solaris Auditing (BSM) enabled. Being able to panic a Solaris
Auditing enabled system is a type of Denial of Service (DoS).
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
* Solaris 9 without patch 122300-06
x86 Platform
* Solaris 9 without patch 122301-06
Note 1: This issue does not affect Solaris 8 or Solaris 10.
Note 2: This issue only affects systems which have Solaris Auditing
(see bsmconv(1M)) enabled.
To determine if a system has Solaris Auditing enabled the grep(1)
command can be used to search the "/etc/system" file for a reference
to the c2audit kernel module as in the following example:
$ grep c2audit /etc/system
set c2audit:audit_load = 1
Note 3: This issue only occurs on systems where Solaris Auditing has
been configured to audit one of the following audit classes (see
audit_class(4)):
0x00000001:fr:file read
0x00000002:fw:file write
0x00000008:fm:file attribute modify
0x00000010:fc:file create
0x00000020:fd:file delete
To determine which audit classes have been configured on the system
consult the audit_control(4) and audit_user(4) files.
3. Symptoms
Should the described issue occur, the system panics with a stack
backtrace which ends with the following function calls:
bcopy+0x170(300016c86c8, 0, ffffffc7, 38, 0, 300016c86c8)
audit_savepath+0x10c(30000c29048, 0, 0, 30000225b68, 0, 300008c5d40)
lookuppnvp+0x80c(30000225b68, 0, 1, 0, 0, 1494400)
[...]
4. Relief/Workaround
Until patches can be applied Solaris Auditing can be configured to not
audit the audit classes mentioned in Section 2 above. This can be done
by modifying the audit_control(4) and audit_user(4) files and then
either rebooting the system or modifying the audit preselection mask
of running processes on the system using auditconfig(1M).
5. Resolution
This issue is addressed in the following releases:
SPARC Platform
* Solaris 9 with patch 122300-06 or later
x86 Platform
* Solaris 9 with patch 122301-06 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-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
iQCVAwUBRjlqTyh9+71yA2DNAQIseAQAlE+DgFTYKshYRywZiEFynp3VNkMTGs3t
ApVMx5Vow8LIdvDrkDmnDO3szs9/1zDtEfXNSnWlNdRwY/VcSVbO5k42nQPFKSCO
B4cJnQDAgaHV1TBSNhw25CYskWBbN5diAkoJwJa5CoSNT8GBgYu23XRu9SXEfx52
HNNx4B11XPg=
=Tr9K
-----END PGP SIGNATURE-----