file is a utility to identify the type of data in a given file based on the file's contents.
file was found to contain an integer underflow vulnerability. If an attacker could get a user to use the file command on a specially crafted file it is possible that arbitrary code could be executed. The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the name CVE-2007-1536 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.1, CM 4.x | Low | Upgrade to CM 5.0 or later. |
| Avaya Intuity LX | IALX 2.0, 2.0SP1 | Low | Upgrade to IALX 2.0 SP2 or later. |
| Avaya EMMC | All | Low | This will not be addressed as no further releases of EMMC are planned. |
| Avaya Messaging Storage Server | MSS 3.x | Low | Upgrade to MSS 4.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.1 and 4.0 | Low | Upgrade to SES 5.0 or later. |
| Avaya AES | AES 4.0 | Low | Update to AES 4.0.1 or later. |
Recommended Actions:
For all system products which use
vulnerable
versions of file, 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: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| CVLAN | All | None | 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) | All | Low | See recommended actions below. |
Recommended Actions:
Avaya recommends that customers follow
recommended actions supplied by RedHat Linux or remove the affected
package.
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 - May 4, 2007 - Initial Statement issued.
V 2.0 - October 9, 2007 - Updated Actions for AES.
V 3.0 - November 21, 2008 - Changed recommended actions for CM and
SES.
V 4.0 - February 16, 2009 - Changed recommended actions for MSS and
EMMC.
V 5.0 - May 22, 2009 - Changed affected versions and recommended actions
for IALX.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].
© 2007 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.