gemirkhanian
asked on
Directory traversal vulnerability in Exchange 2010 Sp3
Has anyone encountered this before? When we search for this we have found issues pertaining to Exchange 2003 but nothing relating to Exchange 2010.
We are running Exchange 2010 SP3 with Rollup 4 on a Windows Server 2008 R2 Enterprise
Our Trustwave Vulnerability scan came back with the following finding:
https://exchange.blah.com/owa/auth/logon.aspx
The web server detected running on the system is vulnerable to a directory traversal vulnerability. A directory traversal vulnerability accesses files and directories that are stored outside the web root folder.
Evidence:
GET /owa/auth/logon.aspx?..%2F
Accept: */*
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Host: exchange.blah.com
HTTP/1.1 200 OK
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Set-Cookie: OutlookSession=36c13b44a53
X-OWA-Version: 14.3.174.1
X-Powered-By: ASP.NET
Date: Sat, 22 Mar 2014 05:02:57 GMT
Content-Length: 8779
Thanks in advance for your input.
We are running Exchange 2010 SP3 with Rollup 4 on a Windows Server 2008 R2 Enterprise
Our Trustwave Vulnerability scan came back with the following finding:
https://exchange.blah.com/owa/auth/logon.aspx
The web server detected running on the system is vulnerable to a directory traversal vulnerability. A directory traversal vulnerability accesses files and directories that are stored outside the web root folder.
Evidence:
GET /owa/auth/logon.aspx?..%2F
Accept: */*
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Host: exchange.blah.com
HTTP/1.1 200 OK
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Set-Cookie: OutlookSession=36c13b44a53
X-OWA-Version: 14.3.174.1
X-Powered-By: ASP.NET
Date: Sat, 22 Mar 2014 05:02:57 GMT
Content-Length: 8779
Thanks in advance for your input.
The extract is from the link below. This flagging if alert is likely due to the IIS in Exchange. Have it check again as Urlscan should not be needed in 2010. Also if specific CVE is shown in trustwave scan findings then it is then even more worrisome. We need to close low hanging
Http://technet.microsoft.com/en-us/library/bb691338(v=exchg.141).aspx
The Exchange Best Practices Analyzer is one of the most effective tools that you can run regularly to help verify that your Exchange environment is secure. The Exchange Best Practices Analyzer automatically examines your Microsoft Exchange deployment and determines whether it's configured according to Microsoft best practices. In Exchange 2010, the Exchange Best Practices Analyzer is installed as part of Exchange Setup and can be run from the Tools section of the Exchange Management Console (EMC).
Http://technet.microsoft.com/en-us/library/bb691338(v=exchg.141).aspx
The Exchange Best Practices Analyzer is one of the most effective tools that you can run regularly to help verify that your Exchange environment is secure. The Exchange Best Practices Analyzer automatically examines your Microsoft Exchange deployment and determines whether it's configured according to Microsoft best practices. In Exchange 2010, the Exchange Best Practices Analyzer is installed as part of Exchange Setup and can be run from the Tools section of the Exchange Management Console (EMC).
ASKER
There was no CVE provided. Is this a false positive I can report or is this a real problem I need to remediate if the best practices analyzer finds that everything is setup correctly?
At least, it is not mapping to a known vulnerability. Scanning has tendency for false positive and it is always best to substantiate why it is false positive with another separate justification that appropriate hardening is performed.
Good to run the analyser to ascertain the level of hardening and patch level e.g.
a) Run the MBSA - http://technet.microsoft.com/en-US/security/cc184924.aspx
b) Run the Analyser - http://technet.microsoft.com/en-us/library/bb508838(EXCHG.80).aspx
The useful part for above is that they will recommend action to address or mitigate any finding of concern. E.g.For every issue, the Exchange Server Best Practices Analyzer provides three kinds of data:
It reports what it found in the Exchange Server organization that it scanned.
It provides a recommended configuration.
It provides links to more detailed information about the issue and related topics.
Good to run the analyser to ascertain the level of hardening and patch level e.g.
a) Run the MBSA - http://technet.microsoft.com/en-US/security/cc184924.aspx
b) Run the Analyser - http://technet.microsoft.com/en-us/library/bb508838(EXCHG.80).aspx
The useful part for above is that they will recommend action to address or mitigate any finding of concern. E.g.For every issue, the Exchange Server Best Practices Analyzer provides three kinds of data:
It reports what it found in the Exchange Server organization that it scanned.
It provides a recommended configuration.
It provides links to more detailed information about the issue and related topics.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thank you for posting this, we were flagged for the same and your post has helped me to resolve it!
By the way, our dispute was Denied.
By the way, our dispute was Denied.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for gemirkhanian's comment #a39978714
for the following reason:
Problem was a false positive, vendor support had to be contacted to determine this.
Accepted answer: 0 points for gemirkhanian's comment #a39978714
for the following reason:
Problem was a false positive, vendor support had to be contacted to determine this.
glad to have help, but will seek your help to mark the useful advice so that community can benefit else they may get the impression it is not of use
To share as I see may be useful in grading the answer, for considerations.
Please post your solution; then accept your own comment as the answer.
http://support.experts-exchange.com/customer/portal/articles/626549 self-answered
http://support.experts-exchange.com/customer/portal/articles/626862 self-answered with help
http://support.experts-exchange.com/customer/portal/articles/481419 grading
Please post your solution; then accept your own comment as the answer.
http://support.experts-exchange.com/customer/portal/articles/626549 self-answered
http://support.experts-exchange.com/customer/portal/articles/626862 self-answered with help
http://support.experts-exchange.com/customer/portal/articles/481419 grading
ASKER
They denied my first dispute as well (after 8 days of waiting).
We talked to support and they said we need to make the statement that there is no directory traversal and that we are not leaking information. I then copied and pasted the email that support sent us about it and referenced the ticket number.
The dispute has now been approved.
We talked to support and they said we need to make the statement that there is no directory traversal and that we are not leaking information. I then copied and pasted the email that support sent us about it and referenced the ticket number.
The dispute has now been approved.
thanks for sharing. looks like my advices have helped
They denied our dispute as well, I have resubmitted with the notes above. When I called support they said they couldn't resolve over the phone and to resubmit online. I never received an email or instructions on how to word it to be accepted, so hopefully they take the second time.
Running on a fully patched SBS2011 with iis 7.5.