Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.0109 -- [Solaris]
A number of vulnerabilities have been identified in Avaya
Systems products using Solaris
30 January 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: libxml2
lpadmin(1M)
ppdmgr(1M)
libike
(pty(7D))
Publisher: Avaya
Operating System: Solaris
OpenSolaris
Impact: Denial of Service
Access: Remote/Unauthenticated
CVE Names: CVE-2008-3529 CVE-2009-0167 CVE-2009-0168
CVE-2009-0267 CVE-2009-0268
Ref: ESB-2009.0055
ESB-2009.0066
ESB-2009.0089
ESB-2009.0090
Original Bulletin:
http://support.avaya.com/elmodocs2/security/ASA-2009-025.htm
http://support.avaya.com/elmodocs2/security/ASA-2009-026.htm
http://support.avaya.com/elmodocs2/security/ASA-2009-032.htm
http://support.avaya.com/elmodocs2/security/ASA-2009-034.htm
Comment: This ESB contains four (4) advisories regarding vulnerabilities in
Solaris as used by Avaya.
- --------------------------BEGIN INCLUDED TEXT--------------------
A Security Vulnerability in the libxml2 Library May Lead to Denial of
Service (DoS) (Sun 247346)
Original Release Date: January 28, 2009
Last Revised: January 28, 2009
Number: ASA-2009-025
Risk Level: Low
Advisory Version: 1.0
Advisory Status: Interim
1. Overview:
A new Sun Alert Notification from Sun Microsystems has been issued and is
described below. Additional information about this issue may be found on the
sunsolve.sun.com website, although a maintenance contract with Sun may be
required to view the information.
247346
A Security Vulnerability in the libxml2 Library May Lead to Denial of
Service (DoS)
Product: Solaris 9 Operating System, Solaris 10 Operating System
Category: Security
Date Released: 15-Jan-2009
http://sunsolve.sun.com/search/document.do?assetkey=1-66-247346-1
2. Avaya System Products using a Sun Microsystems Operating System with
libxml2 installed:
Some Avaya system products are delivered with an Operating System from Sun
Microsystems. Actions to be taken on these products are described below.
Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R13/R13.1, R14/R14.1, R15 Low This issue will be
addressed in accordance with section five of Avaya's Product Security
Vulnerability Response Policy
Recommended Actions:
For all vulnerable system products, Avaya recommends that customers restrict
local and network access to the server. This restriction should be enforced
through the use of physical security, firewalls, ACLs, VPNs, and other
generally-accepted networking practices until such time as an update becomes
available and can be installed.
3. 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.
4. 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 BUT NOT LIMITED TO 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, INCIDENTAL, STATUTORY, 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.
5. Revision History:
V 1.0 - January 28, 2009 - Initial Statement issued.
Send information regarding any discovered security problems with Avaya
products to either the contact noted in the product's documentation or
securityalerts@avaya.com.
2009 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.
- -------------------------------------------------------------------------------
Security Vulnerabilities in the Solaris lpadmin(1M) and ppdmgr(1M) Utilities
May Lead to a Denial of Service (DoS) Condition (Sun 249306)
Original Release Date: January 28, 2009
Last Revised: January 28, 2009
Number: ASA-2009-026
Risk Level: Low
Advisory Version: 1.0
Advisory Status: Interim
1. Overview:
A new Sun Alert Notification from Sun Microsystems has been issued and is
described below. Additional information about this issue may be found on the
sunsolve.sun.com website, although a maintenance contract with Sun may be
required to view the information.
249306
Security Vulnerabilities in the Solaris lpadmin(1M) and ppdmgr(1M)
Utilities May Lead to a Denial of Service (DoS) Condition
Product: Solaris 10 Operating System, OpenSolaris
Category: Security
Date Released: 13-Jan-2009
http://sunsolve.sun.com/search/document.do?assetkey=1-66-249306-1
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned
the names CVE-2009-0167 and CVE-2009-0168 to these issues.
2. Avaya System Products using a Sun Microsystems Operating System:
Some Avaya system products are delivered with an Operating System from Sun
Microsystems. Actions to be taken on these products are described below.
Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R15 Low This issue will be addressed in accordance
with section five of Avaya's Product Security Vulnerability Response Policy
Avaya IR 2.0 on Solaris 10, 3.0 Low This issue will be addressed
in accordance with section five of Avaya's Product Security Vulnerability
Response Policy
Recommended Actions:
For all vulnerable system products, Avaya recommends that customers restrict
local and network access to the server. This restriction should be enforced
through the use of physical security, firewalls, ACLs, VPNs, and other
generally-accepted networking practices until such time as an update becomes
available and can be installed.
3. 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.
4. 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 BUT NOT LIMITED TO 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, INCIDENTAL, STATUTORY, 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.
5. Revision History:
V 1.0 - January 28, 2009 - Initial Statement issued.
Send information regarding any discovered security problems with Avaya
products to either the contact noted in the product's documentation or
securityalerts@avaya.com.
2009 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.
- -------------------------------------------------------------------------------
Security Vulnerability with IKE Packet Handling in Solaris libike Library
may Lead to a Crash of in.iked(1M) (Sun 247406)
Original Release Date: January 28, 2009
Last Revised: January 28, 2009
Number: ASA-2009-032
Risk Level: Low
Advisory Version: 1.0
Advisory Status: Interim
1. Overview:
A new Sun Alert Notification from Sun Microsystems has been issued and is
described below. Additional information about this issue may be found on
the sunsolve.sun.com website, although a maintenance contract with Sun may
be required to view the information.
247406
Security Vulnerability with IKE Packet Handling in Solaris libike
Library may Lead to a Crash of in.iked(1M)
Product: Solaris 9 Operating System, Solaris 10 Operating System,
OpenSolaris
Category: Security
Date Released: 22-Jan-2009
http://sunsolve.sun.com/search/document.do?assetkey=1-66-247406-1
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned
the name CVE-2009-0267 to this issue.
2. Avaya System Products using a Sun Microsystems Operating System:
Some Avaya system products are delivered with an Operating System from Sun
Microsystems. Actions to be taken on these products are described below.
Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R13/R13.1, R14/R14.1, R15 Low This issue will be
addressed in accordance with section five of Avaya's Product Security
Vulnerability Response Policy
Avaya IR 2.0 on Solaris 10, 3.0, 4.0 Low Although in.iked
service is installed on IR by default, it is not enabled, configured, or
supported. Patches for the in.iked service will not be tesed by Avaya for
installation on IR.
Recommended Actions:
For all vulnerable system products, Avaya recommends that customers restrict
local and network access to the server. This restriction should be enforced
through the use of physical security, firewalls, ACLs, VPNs, and other
generally-accepted networking practices until such time as an update becomes
available and can be installed.
3. 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.
4. 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 BUT NOT LIMITED TO 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, INCIDENTAL, STATUTORY, 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.
5. Revision History:
V 1.0 - January 28, 2009 - Initial Statement issued.
Send information regarding any discovered security problems with Avaya
products to either the contact noted in the product's documentation or
securityalerts@avaya.com.
2009 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.
- -------------------------------------------------------------------------------
Security Vulnerability in the Solaris Pseudo-terminal Driver (pty(7D)) may
Cause a System Panic (Sun 249586)
Original Release Date: January 28, 2009
Last Revised: January 28, 2009
Number: ASA-2009-034
Risk Level: Low
Advisory Version: 1.0
Advisory Status: Interim
1. Overview:
A new Sun Alert Notification from Sun Microsystems has been issued and is
described below. Additional information about this issue may be found on the
sunsolve.sun.com website, although a maintenance contract with Sun may be
required to view the information.
249586
Security Vulnerability in the Solaris Pseudo-terminal Driver (pty(7D))
may Cause a System Panic
Product: Solaris 8 Operating System, Solaris 9 Operating System,
Solaris 10 Operating System, OpenSolaris
Category: Security
Date Released: 22-Jan-2009
http://sunsolve.sun.com/search/document.do?assetkey=1-66-249586-1
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned
the name CVE-2009-0268 to this issue.
2. Avaya System Products using a Sun Microsystems Operating System:
Some Avaya system products are delivered with an Operating System from Sun
Microsystems. Actions to be taken on these products are described below.
Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R13/R13.1, R14/R14.1, R15 Low This issue will be
addressed in accordance with section five of Avaya's Product Security
Vulnerability Response Policy
Avaya IR 2.0, 3.0, 4.0 Low IR systems do not configure, use, or
support pseudo-terminals. Therefore Avaya will not test the recommended patch.
Recommended Actions:
For all vulnerable system products, Avaya recommends that customers restrict
local and network access to the server. This restriction should be enforced
through the use of physical security, firewalls, ACLs, VPNs, and other
generally-accepted networking practices until such time as an update becomes
available and can be installed.
3. 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.
4. 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 BUT NOT LIMITED TO 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, INCIDENTAL, STATUTORY, 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.
5. Revision History:
V 1.0 - January 28, 2009 - Initial Statement issued.
Send information regarding any discovered security problems with Avaya
products to either the contact noted in the product's documentation or
securityalerts@avaya.com.
2009 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.
- --------------------------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
iQCVAwUBSYJyACh9+71yA2DNAQJ0TAP+NuWR7+qXtnWm5YwhDbb/68gQxZRkZt6x
lPZuZqgHZE5UAHbwJE7djgydMLrtYhbLopQ7WZ4h5bG5kfXoOG+kW3FGhb7Awjav
uP0kXoPCAFFW5tyr5fhJSCWckAE9fzFp//V7s9Z8tdtZNbawAdWrp5KIZerV1QAu
O9vfuzfy70E=
=FpFc
-----END PGP SIGNATURE-----