The Pluggable Authentication Modules (PAM) provide a way for administrators to create and change authentication policies without major changes to the programs that handle authentication.
PAM's pam_console module was found to contain an issue in the way it set console device permissions. A console device could possibly retain the ownership of the console user after the console user logged out, allowing for a potential information leak to other local users. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-1716 to this issue.
The PAM library was found to have an issue in how it wrote account names to the audit subsystem. If an attacker used this to inject text containing parts of an audit message, it could cause audit log parsing tools to show misleading and/or confusing messages. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-3102 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Communication Manager | CM 3.x, 4.x, 5.0 | Low | Upgrade to CM 5.1 or later. |
| Avaya Intuity Audix LX | IALX 2.0, 2.0 SP1 | Low | Upgrade to IALX 2.0 SP2 or later. |
| Avaya Messaging Storage Server | MSS 3.x, 4.0 | Low | Upgrade to MSS 5.0 or later. |
| Avaya Message Networking | MN 3.1 | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
| Avaya CCS/SES | SES 3.1.x, 4.0, 5.0 | Low | Upgrade to SES 5.1 or later. |
| Avaya AES | AES 4.0, 4.0.1, 4.1 | Low | Upgrade to AES 4.2 or later. |
Recommended Actions:
For all system products which use
vulnerable
versions of PAM, 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.
Avaya software-only products operate on general-purpose operating systems. Occasionally vulnerabilities may be discovered in the underlying operating system or applications that come with the operating system. These vulnerabilities often do not impact the software-only product directly but may threaten the integrity of the underlying platform.
In the case of this advisory Avaya software-only products are not affected by the vulnerability directly but the underlying Linux platform may be. Customers should determine on which Linux operating system the product was installed and then follow that vendor's guidance.
| Product: | Actions: |
|---|---|
| CVLAN | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application. The CVLAN application does not require the software described in this advisory. |
| Avaya Integrated Management Suite (IMS) | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application. The IMS application does not require the software described in this advisory. |
Recommended Actions:
In the event that the affected package
is
installed, Avaya recommends that customers follow recommended actions
supplied
by RedHat Linux.
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.
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.
V 1.0 - January 2, 2008 - Initial Statement issued.
V 2.0 - September 9, 2008 - Changed CM, SES, and AES affected versions
and recommended actions.
V 3.0 - January 6, 2009 - Changed IALX recommended actions.
V 4.0 - March 3, 2009 - Changed IALX affected versions and MSS affected
versions and recommended actions.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].
© 2008 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.