|
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. Home >> Browse Vulnerability Assessment Database >> Gentoo Local Security Checks >> [GLSA-200612-15] McAfee VirusScan: Insecure DT_RPATH Vulnerability Assessment Details
|
[GLSA-200612-15] McAfee VirusScan: Insecure DT_RPATH |
||
McAfee VirusScan: Insecure DT_RPATH Detailed Explanation for this Vulnerability Assessment The remote host is affected by the vulnerability described in GLSA-200612-15 (McAfee VirusScan: Insecure DT_RPATH) Jakub Moc of Gentoo Linux discovered that McAfee VirusScan was distributed with an insecure DT_RPATH which included the current working directory, rather than $ORIGIN which was probably intended. Impact A possible hacker could entice a VirusScan user to scan an arbitrary file and execute arbitrary code with the rights of the VirusScan user by tricking the dynamic loader into loading an untrusted ELF DSO. An automated system, such as a mail scanner, may be subverted to execute arbitrary code with the rights of the process invoking VirusScan. Workaround Do not scan files or execute VirusScan from an untrusted working directory. References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6474 Solution: As VirusScan verifies that it has not been modified before executing, it is not possible to correct the DT_RPATH. Furthermore, this would violate the license that VirusScan is distributed under. For this reason, the package has been masked in Portage pending the resolution of this issue. # emerge --ask --verbose --unmerge "app-antivirus/vlnx" Network Security Threat Level: High Networks Security ID: Vulnerability Assessment Copyright: (C) 2006 Michel Arboi |
||
Cables, Connectors |
|
||
No Discussions have been posted on this vulnerability. |