Hello,

We are using SBS 2003 Premium and have an account for Hackersafe, which test
every day our server for vulnerabilities. The last few weeks we got a report
that this server is not hackersafe. The report says that it found an Blind MS
SQL Injection Vulnerability. The server is fully patched! Sometimes when we
do an on demand scan at hackersafe, there is no problem, but after a few days
the vulnerability shows again.

The Blind MS SQL Injection vulnerability is found at the following point:

Protocol https Port 443 Read Timeout 20000 Method POST Demo
Path /exchweb/bin/auth/owaauth.dll
Headers
Referer=https%3A%2F%2Fmydomain.xxx%3A443%2Fexchweb%2Fbin%2Fauth%2Fowalogon.asp%3Furl%3D%2522Xx%253CXaXaXXaXaX%253ExX%26reason%3D0
Content-Type=application%2Fx-www-form-urlencoded

Body destination="1 declare @x varchar(99) set
@x=0x77616974666f722064656c61792027303a303a323027 exec(@x)--<XaXaXXaXaX>xX
flags=0
username=0
password=0
SubmitCreds=Log On
trusted=0

Can someone please advise how to solve this ? We are using Outlook Web Access.

Re: Hackersafe: Blind MS SQL Injection Vulnerability by Susan

Susan
Tue May 06 23:50:35 PDT 2008

Robbert Tol wrote:
> Hello,
>
> We are using SBS 2003 Premium and have an account for Hackersafe, which test
> every day our server for vulnerabilities. The last few weeks we got a report
> that this server is not hackersafe. The report says that it found an Blind MS
> SQL Injection Vulnerability. The server is fully patched! Sometimes when we
> do an on demand scan at hackersafe, there is no problem, but after a few days
> the vulnerability shows again.
>
> The Blind MS SQL Injection vulnerability is found at the following point:
>
> Protocol https Port 443 Read Timeout 20000 Method POST Demo
> Path /exchweb/bin/auth/owaauth.dll
> Headers
> Referer=https%3A%2F%2Fmydomain.xxx%3A443%2Fexchweb%2Fbin%2Fauth%2Fowalogon.asp%3Furl%3D%2522Xx%253CXaXaXXaXaX%253ExX%26reason%3D0
> Content-Type=application%2Fx-www-form-urlencoded
>
> Body destination="1 declare @x varchar(99) set
> @x=0x77616974666f722064656c61792027303a303a323027 exec(@x)--<XaXaXXaXaX>xX
> flags=0
> username=0
> password=0
> SubmitCreds=Log On
> trusted=0
>
> Can someone please advise how to solve this ? We are using Outlook Web Access.
>
>
Two things of concern here.

1. Hackersafe has deemed some web sites as safe when they've been owned
already, so I'm not sure that I think they are credible or merely crying
wolf here.

2. I'm wondering if they are a bit overreacting to the recent SQL
injection reports.

Let me ask up the ladder and hang loose for now.