[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

UNIRAS Brief - 592/03 - Sun Microsystems Alert Notification



 
-----BEGIN PGP SIGNED MESSAGE-----

- ----------------------------------------------------------------------------------
   UNIRAS (UK Govt CERT) Briefing Notice - 592/03 dated 30.10.03  Time: 10:25
 UNIRAS is part of NISCC(National Infrastructure Security Co-ordination Centre)
- ---------------------------------------------------------------------------------- 
  UNIRAS material is also available from its website at www.uniras.gov.uk and
         Information about NISCC is available from www.niscc.gov.uk
- ----------------------------------------------------------------------------------
Title
=====
Solaris NFS Server: Possible Denial of Servive.

Detail
====== 
When a Solaris NFS Server receives certain invalid requests from a
client for a shared UFS file system, it may cause a UFS panic on the
server. When the server reboots after the panic, the client may retry
the same request, causing the server to panic again, resulting in a
panic/reboot loop.

- -----------------------------------------------------------------------------------
Product:                NFS
Publisher:              Sun Microsystems
Operating System:       Solaris 9
                        Solaris 8
                        Solaris 7
Impact:                 Denial of Service
Access Required:        Remote

Original bulletin:

         http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert%2F57406


   DOCUMENT ID: 57406
   SYNOPSIS: NFS Server May Panic Upon Receipt of Certain Invalid Client
   Requests
   DETAIL DESCRIPTION:
   
Sun(sm) Alert Notification

     * Sun Alert ID: 57406
     * Synopsis: NFS Server May Panic Upon Receipt of Certain Invalid
       Client Requests
     * Category: Security
     * Product: Solaris
     * BugIDs: 4854840
     * Avoidance: Patch
     * State: Resolved
     * Date Released: 27-Oct-2003
     * Date Closed: 27-Oct-2003
     * Date Modified:
       
1. Impact

   When a Solaris NFS Server receives certain invalid requests from a
   client for a shared UFS file system, it may cause a UFS panic on the
   server. When the server reboots after the panic, the client may retry
   the same request, causing the server to panic again, resulting in a
   panic/reboot loop.
   
2. Contributing Factors

   This issue can occur in the following releases:
   
   SPARC Platform
     * Solaris 7 without patch 106541-27
     * Solaris 8 without patch 108528-24
     * Solaris 9 without patch 113454-11
       
   x86 Platform
     * Solaris 7 without patch 106542-27
     * Solaris 8 without patch 108529-24
     * Solaris 9 without patch 114563-07
       
   The issue described will only occur on specific forms of invalid
   requests; most malformed requests are detected and result in an error
   being returned to the client.
   
   Notes: 
    1. Solaris 2.6 will not be evaluated regarding the potential impact
       of the issue described in this Sun Alert.
    2. Solaris NFS Clients do not issue the specific type of request
       which causes the UFS panic.
    3. Some Linux systems have been observed to cause this issue when
       sending NFS client requests to a Solaris NFS Server.
       
3. Symptoms

   The system panics with a "NULL pointer dereference" message similar to
   the following:
    BAD TRAP: type=31 rp=2a103176cc0 addr=8 mmu_fsr=0
    occurred in module "ufs" due to a NULL pointer dereference                 
 

   As noted above, the server may panic again upon reboot, due to the
   client retrying the same, malformed request.
   SOLUTION SUMMARY:
   
4. Relief/Workaround

   If the NFS client which is issuing the malformed requests can be
   identified, then rebooting this client or removing it from the network
   will break the server panic/reboot cycle. Alternatively, the file
   system(s) being accessed by this client may be shared "read-only".
   
   If the NFS client cannot be identified, the NFS server must first be
   booted into single user mode. The share must then be disabled on the
   file system which the client is accessing, or the file system must be
   shared "read-only". If the share cannot be isolated to a specific file
   system, then all file systems must be temporarily shared "read-only"
   until the required patch is applied.
   
   Note: Please see the share(1M) man page for options on file system
   sharing.
   
5. Resolution

   This issue is addressed in the following releases:
   
   SPARC Platform
     * Solaris 7 with patch 106541-27 or later
     * Solaris 8 with patch 108528-24 or later
     * Solaris 9 with patch 113454-11 or later
       
   x86 Platform
     * Solaris 7 with patch 106542-27 or later
     * Solaris 8 with patch 108529-24 or later
     * Solaris 9 with patch 114563-07 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-2003 Sun Microsystems, Inc., 4150 Network Circle, Santa
   Clara, CA 95054 U.S.A. All rights reserved.
   
- ----------------------------------------------------------------------------------
For additional information or assistance, please contact the HELP Desk by 
telephone or Not Protectively Marked information may be sent via EMail to:
uniras@xxxxxxxxxxxx

Office Hours:
Mon - Fri: 08:30 - 17:00 Hrs
Tel: +44 (0) 20 7821 1330 Ext 4511
Fax: +44 (0) 20 7821 1686

Outside of Office Hours:
On Call Duty Officer:
Tel: +44 (0) 20 7821 1330 and follow the prompts

- ----------------------------------------------------------------------------------
UNIRAS wishes to acknowledge the contributions of Sun Microsystems for the
information contained in this Briefing. 
- ----------------------------------------------------------------------------------
This Briefing contains the information released by the original author. Some 
of the information may have changed since it was released. If the vulnerability 
affects you, it may be prudent to retrieve the advisory from the canonical site 
to ensure that you receive the most current information concerning that problem.

Reference to any specific commercial product, process, or service by trade 
name, trademark manufacturer, or otherwise, does not constitute or imply 
its endorsement, recommendation, or favouring by UNIRAS or NISCC.  The views 
and opinions of authors expressed within this notice shall not be used for 
advertising or product endorsement purposes.

Neither UNIRAS or NISCC shall also accept responsibility for any errors 
or omissions contained within this briefing notice. In particular, they shall 
not be liable for any loss or damage whatsoever, arising from or in connection 
with the usage of information contained within this notice.

UNIRAS is a member of the Forum of Incident Response and Security Teams (FIRST) 
and has contacts with other international Incident Response Teams (IRTs) in 
order to foster cooperation and coordination in incident prevention, to prompt 
rapid reaction to incidents, and to promote information sharing amongst its 
members and the community at large. 
- ----------------------------------------------------------------------------------
<End of UNIRAS Briefing>
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0

iQCVAwUBP6DmeIpao72zK539AQEc5gP+OwgTD163ckYr0hp1EPTWa8gC53WL56SY
XCncU+GszYPDEmyIM5tUStu4+gHybCUfxNxm2yV/BdeQoD50ENAF0habCN4Z8ylE
AbRLBZv7TDvEkEA92Bu/julqhZr2yw0hlw5M4DaBLd92JlWGjYaeBLt8Q8SpkaK+
Dwl9XM7epps=
=oMn8
-----END PGP SIGNATURE-----