Sun Alert Notifications from Sun Weekly Report dated Jun 17, 2006

Original Release Date: August 14, 2006
Last Revised: November 9, 2006
Number: ASA-2006-148
Risk Level: Low
Advisory Version: 3.0
Advisory Status: Final

1. Overview:

New Sun Alert Notifications from Sun Microsystems have been issued and are described below. Issues which have been resolved by Sun Microsystems have been indicated as such. Notifications without a resolution may have restrictions to additional information on the sunsolve.sun.com website.

102460
A Security Vulnerability in sendmail(1M) Versions Prior to 8.13.7 May Allow a Denial of Service (DoS) To Occur
Product: Solaris 9 Operating System, Solaris 10 Operating System, Solaris 8 Operating System
Category: Security
Date Released: 14-Jun-2006
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102460-1
102461
Memory Leak in NSS May Cause the System to Hang or Panic
Product: Sun Java Enterprise System 2003Q4, Sun Java Enterprise System 2005Q1, Sun Java Enterprise System 2004Q2
Category: Availability
Date Released: 13-Jun-2006
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102461-1

Avaya System Products using a Sun Microsystems Operating System:
Avaya system products include an Operating System with the product when it is delivered. The Avaya Call Management System (CMS) and the Avaya Interactive Response (IR) are both shipped with an operating system from Sun Microsystems. Actions to be taken on those products are described below.

Recommended Actions:
Follow the recommended actions for each notification described below. This advisory will be updated as additional information becomes available.

Sun Advisory: Affected S/W Version Risk Comments or Recommended Actions
102460 IR - All

CMS - V9, V11, R12, R13, R13.1
Low

Low
IR - The patch 122856-02 from Sun may be applied to the IR system.

CMS V9, V11 - Apply patch 113575-07 or subsequent.
CMS R12, R13, R13.1 - Apply patch 113575-07 or subsequent.
102461 All None No action is necessary. IR and CMS do not utilize Sun Java Enterprise System

Recommended Actions:
To prevent the disruption of the sendmail(1M) delivery mechanism, the 'ForkEachJob' option can be set, causing sendmail to deliver each message in its own process, preventing any one message from disrupting the delivery of other messages. However, this may have an impact on the performance of the delivery process.

This option can be set by adding the following line to the *.mc files used to generate the "/etc/mail/sendmail.cf" and "/etc/mail/submit.cf" (if present) files:

define(`confSEPARATE_PROC',`true')dnl


The *.mc files are located in "/usr/lib/mail/cf" for Solaris 8 and 9.
Generate the new *.cf files from these revised *.mc files and copy to "/etc/mail/sendmail.cf" and "/etc/mail/submit.cf" as required. Please refer to "/usr/lib/mail/README" for additional information on how to use the *.mc files.

Restart sendmail once the modifications have been performed, as follows:

Solaris 8, 9:

# /etc/init.d/sendmail stop
# /etc/init.d/sendmail start


To prevent sendmail(1M) from filling up the disk, it can be configured using the coreadm(1M) command to write statically named core files. This should be applied to both the global core file pattern (if enabled) and the per-process core file pattern.

For example, to disable global core files:

# coreadm -d global


and to make sendmail core dump filenames static until the sendmail service is restarted:

# coreadm -p core.%f $(pgrep sendmail)

2. Additional Information:

Additional information may also be available via the Avaya support website and through your Avaya account representative. Please contact your Avaya product support representative, or dial 1-800-242-2121, with any questions.

3. Disclaimer:

ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS' SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.

4. Revision History:

V 1.0 - August 14, 2006 - Initial Statement issued.
V 2.0 - November 6, 2006 - Updated Advisory Status from Final to Interim based on further review and corrected grammatical error.
V 3.0 - November 9, 2006 - Updated Recommended Actions for CMS on Sun Alert ID 102460 and changed the Advisory Status to Final.

Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or securityalerts@avaya.com.

© 2006 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.