[NT] Back Office Web Administration Authentication Bypass

From: support@securiteam.com
Date: 04/18/02


From: support@securiteam.com
To: list@securiteam.com
Date: Thu, 18 Apr 2002 21:45:37 +0200 (CEST)

The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion

When was the last time you checked your server's security?
How about a monthly report?
http://www.AutomatedScanning.com - Know that you're safe.
- - - - - - - - -

  Back Office Web Administration Authentication Bypass
------------------------------------------------------------------------

SUMMARY

With the Microsoft Back Office suite of products comes a web based
administration ASP based application that runs on IIS. Normally, to use
the administration pages a user must authenticate but NGSSoftware have
discovered that it is trivial to bypass this.

DETAILS

Vulnerable systems:
 * Microsoft's Back Office Web Administrator 4.0
 * Microsoft's Back Office Web Administrator 4.5

Each of the Back Office Web Administrator ASP pages checks to see if the
user has been authenticated but does this with the following snippet of
code

 If Request.ServerVariables("auth_type") = "" Then
  Response.Status = "401 ACCESS DENIED"
  Response.End
 End If

This is the only "authorization/authentication" performed. As such it's
trivial to bypass:

  GET /BOADMIN/BACKOFFICE/SERVICES.ASP HTTP/1.1
  Host: hostname
  Authorization: Basic
 [enter]
 [enter]

No credentials are required as, technically the auth_type environment
variable has been set, regardless of whether a user name or password have
been supplied.

Risk and Mitigating Factors:
By default, the Back Office Web Administrator is limited to the loop-back
address (127.0.0.1) which means that it cannot be accessed remotely.
However, it is not uncommon to change this to allow for remote
administration; tying the Administrator to the loop-back address makes it
useless.

Basic authentication also needs to be enabled which, again, is not
uncommon.

Fix Information:
For those that match this criterion they are strongly urged to obtain the
patch from Microsoft. Please see
<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316838>
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316838 for more
details.

ADDITIONAL INFORMATION

The information has been provided by <mailto:nisr@ngssoftware.com>
NGSSoftware Insight Security Research.

========================================

This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com

====================
====================

DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.



Relevant Pages

  • Re: [ok] [Full-Disclosure] RE: [Full-Disclosure]MS should re-write code with security in mind
    ... almost all Windows users demand backward compatibility. ... > security upgrades available on MS's site. ... > and authenticate all mail transfer. ...
    (Full-Disclosure)
  • Re: Security Logging in ADAM
    ... How does an anonymous login authenticate anyone? ... If a bind was performed against ADAM, there should be a matching audit event ... in the security event log on the ADAM machine assuming that logon events are ...
    (microsoft.public.windows.server.active_directory)
  • Re: IAS & Fully-Qualified-User-Name
    ... Svyatoslav Pidgorny, MS MVP - Security, MCSE -= F1 is the key =- "Bryan Hunt" wrote in message ... > Logon Failure: ... > Caller User Name: MANAGE1$ ... >>> None of them will authenticate the user. ...
    (microsoft.public.security)
  • Re: NTLM authentication
    ... If I authenticate as I did againt ADAM with their login/pwd, ... Clear the Security EventLog and watch the security events after each bind. ... Note that this can' be done on NT4, so you can only watch the local logon attempts. ... Now, use the "domain\\user" syntax for the username in your DirectoryEntry constructor, where domain is your logon domain and user a domain account. ...
    (microsoft.public.dotnet.languages.csharp)
  • [UNIX] Perl Module pam_per_user Authentication Bypassing
    ... Get your security news from a reliable source. ... There is a security flaw in the pam_per_user PAM module that can allow ... user to an alternate PAM service name that should be used to authenticate ... foo ...
    (Securiteam)