Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R1] McAfee Email and Web Security / Email Gateway Multiple Vulnerabilities



1) McAfee Email and Web Security and Email Gateway contains a flaw related to the /admin/cgi-bin/localadmin script. The issue is due to the script calling the SCMAdmin::AuthManagement::localLogin() function when $ENV{WS_SOURCE_IP} is However, the SCMAdminUtils::setSCMEnvironment() function allows a remote attacker to manipulate the IP passed to the system via the X-Forwarded-for HTTP header allowing them to bypass authentication and gain administrative privileges.

The localadmin script calls SCMAdmin::AuthManagement::localLogin when $ENV{WS_SOURCE_IP} is

     28 # Set up the rest of the environment
     29 setSCMEnvironment(\%cookieInfo);
     30 my ($sid, $err) = ("", "");
     32 binmode(STDOUT, ":utf8");
     34 # Are we being invoked from localhost?
     35 if ("" eq $ENV{WS_SOURCE_IP}) {
     36     unless (SCMAdmin::AuthManagement::localLogin(\$sid, \$err)) {
     37         errorDocument($err);
     38     }
     39 }

SCMAdminUtils::setSCMEnvironment (line 29) allows an attacker to control $ENV{WS_SOURCE_IP} via the X-Forwarded-for HTTP header:

   1049     $ENV{WS_SOURCE_IP} = "";
   1050     if (exists($ENV{HTTP_X_FORWARDED_FOR})) {
   1052     }
   1053     elsif (exists($ENV{REMOTE_ADDR})) {
   1054         $ENV{WS_SOURCE_IP} = $ENV{REMOTE_ADDR};
   1055     }

Note that the CVSSv2 score in this advisory reflects this specific issue.

2) McAfee Email Gateway contains a flaw that allows traversing outside of a restricted path. The issue is due to the /admin/cgi-bin/mui/combo script not properly sanitizing user input, specifically path traversal style attacks (e.g. '../') supplied via the URI. With a specially crafted request, a remote attacker can read arbitrary files. Proof-of-concept:


3) McAfee Email and Web Security and Email Gateway contains a flaw that allows a remote cross-site scripting (XSS) attack. This flaw exists because the application does not validate the URI upon submission to the /admin/cgi-bin/plugindashboard/ or /admin/cgi-bin/dashboard/ scripts before returning it to the user. This may allow a user to create a specially crafted request that would execute arbitrary script code in a user's browser within the trust relationship between their browser and the server. Proof-of-concepts:

https://[target]:8080/admin/cgi-bin/dashboard/1234"><img src="123" onerror=javascript:alert("xss")>
https://[target]:8080/admin/cgi-bin/plugindashboard/1234"><img src="123" onerror=javascript:alert("xss")>

Disclosure Timeline

2012-03-27: Initial report sent to McAfee via email
2012-03-27: McAfee acknowledges receiving the report
2012-04-03: Asked McAfee if they've verified the vulnerabilities exist
2012-04-03: McAfee confirms the vulnerabilities exist and will send an update the next week
2012-04-20: Asked McAfee for an update
2012-04-20: McAfee says hotfixes are currently in testing
2012-05-04: Asked McAfee for an update
2012-05-04: McAfee says the bulletin would be released before close of business
2012-05-04: McAfee says the bulletin would be released COB May 8th if not sooner
2012-05-08: McAfee publishes SB10026

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]