Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
Check for the version of the file packages
Detailed Explanation for this Vulnerability Assessment
Updated file packages are available to close a buffer overflow
[Updated 12 March 2003]
Added packages for Red Hat Enterprise Linux ES and Red Hat Enterprise
The file command is used to identify a particular file according to
the type of data contained by the file.
The file utility before version 3.41 contains a buffer overflow
vulnerability in the ELF parsing routines. This vulnerability may
permit a possible hacker to create a carefully crafted binary which can cause
arbitrary code to run if a victim runs the file command against that
On some distributions it may also be possible to trigger this file command
vulnerability by encouraging the victim to use the
less command on an exploited file name so that it will be processed by the
All users are advised to update to these erratum packages which
contain a backported patch to correct this vulnerability.
Red Hat would like to thank iDefense for disclosing this issue and
zen-parse for discussion of some of the implications.
Solution : http://rhn.redhat.com/errata/RHSA-2003-087.html
Network Security Threat Level: High
Networks Security ID:
Vulnerability Assessment Copyright: This script is Copyright (C) 2004 Tenable Network Security
|Dell Latitude E5580 15.6" Core i5-7300U @2.6GHz 8GB RAM 512GB SSD- Windows 10
|Lenovo Ideapad Yoga 13 13.3" Intel Core i5-3337U @ 1.8GHz 8GB RAM BOOTS NO HDD
|Dell Latitude E7470 14" Core i5-6300U @2.4GHz 8GB RAM 192GB SSD - Windows 10
|Apple iMac 21.5" (Mid-2010) Intel Core i3-3.06Ghz / 8GB RAM / 500GB (MC508LL/A)
No Discussions have been posted on this vulnerability.