McAfee VirusScan 4.03 Alert File Vulnerability
BID:1326
Info
McAfee VirusScan 4.03 Alert File Vulnerability
| Bugtraq ID: | 1326 |
| Class: | Origin Validation Error |
| CVE: | |
| Remote: | No |
| Local: | Yes |
| Published: | Jun 08 2000 12:00AM |
| Updated: | Jun 08 2000 12:00AM |
| Credit: | Posted to Bugtraq on June 8, 2000 by Harry Schmilllson <[email protected]>. |
| Vulnerable: |
McAfee VirusScan 4.0.3 |
| Not Vulnerable: | |
Discussion
McAfee VirusScan 4.03 Alert File Vulnerability
The alerting mechanism in McAfee VirusScan 4.0.3 is accessible by any local user on the network. A local user is capable of sending an unlimited number of alerts to the Central Alert server.
Windows 9x clients send alerts in the form of text files which contain information such as username, computer name, virus name and so forth. This text file could be manipulated by a malicious user to contain arbitrary information. The alerts are stored on the Central Alert server in a directory to which all users have write, read, and delete permissions granted by default.
The alerting mechanism in McAfee VirusScan 4.0.3 is accessible by any local user on the network. A local user is capable of sending an unlimited number of alerts to the Central Alert server.
Windows 9x clients send alerts in the form of text files which contain information such as username, computer name, virus name and so forth. This text file could be manipulated by a malicious user to contain arbitrary information. The alerts are stored on the Central Alert server in a directory to which all users have write, read, and delete permissions granted by default.
Exploit / POC
McAfee VirusScan 4.03 Alert File Vulnerability
See discussion.
See discussion.
Solution / Fix
McAfee VirusScan 4.03 Alert File Vulnerability
Solution:
Currently the SecurityFocus staff are not aware of any vendor supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].
Solution:
Currently the SecurityFocus staff are not aware of any vendor supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].