High APAR - Microsoft: Microsoft Security Bulletin MS02-024: Authentication Flaw in Windows Debugger can Lead to Elevated Privileges (Q320206)

From: Asaf Naaman (Asaf_Naaman/Its-Il@il.ibm.com)
Date: 05/25/02


From: "Asaf Naaman" <Asaf_Naaman/Its-Il@il.ibm.com>
To: focus-ms@securityfocus.com, vuln-dev@securityfocus.com
Date: Sat, 25 May 2002 10:58:06 +0300


- - ----------------------------------------------------------------------
Title: Authentication Flaw in Windows Debugger can Lead to
            Elevated Privileges (Q320206)
Date: 22 May 2002
Software: Microsoft Windows
Impact: Elevation of Privilege
Max Risk: Critical
Bulletin: MS02-024

Microsoft encourages customers to review the Security Bulletin at:
http://www.microsoft.com/technet/security/bulletin/MS02-024.asp.
- - ----------------------------------------------------------------------

Issue:
======

The Windows debugging facility provides a means for programs to
perform diagnostic and analytic functions on applications as they
are running on the operating system. One of these capabilities
allows for a program, usually a debugger, to connect to any running
program, and to take control of it. The program can then issue
commands to the controlled program, including the ability to
start other programs. These commands would then execute in the
same security context as the controlled program.

There is a flaw in the authentication mechanism for the debugging
facility such that an unauthorized program can gain access to the
debugger. A vulnerability results because an attacker can use
this to cause a running program to run a program of her choice.
Because many programs run as the operating system, this means
that an attacker can exploit this vulnerability to run code as
the operating system itself. She could take any action on the
system including deleting data, adding accounts with
administrative access, or reconfiguring the system.

A successful attack requires the ability to logon interactively
to the system, either at the console or through a terminal
session. Also, an a successful attack requires the
introduction of code to exploit this vulnerability.
Because best practices recommends restricting the
ability to logon interactively on servers, this
issue most directly affects client systems and terminal servers.

Mitigating Factors:
====================
 - A successful attack requires the ability to logon interactively
   to the target machine, either directly at the console or
   through a terminal session. Best practices strongly militate
   against ever allowing an unprivileged user to interactively
   log onto business-critical systems such as ERP servers,
   database servers, domain controllers and the like.
   If these recommendations have been followed, the
   vulnerability would principally pose a threat only to
   systems like workstations and terminal servers.

 - A successful attack requires that the attacker be able to
   load code of her choice on the system. Restrictions on a
   user's ability to load and execute arbitrary code could
   potentially prevent a successful attack.

Risk Rating:
============
 - Internet systems: Low
 - Intranet systems: Moderate
 - Client systems: Critical

Patch Availability:
===================
 - A patch is available to fix this vulnerability. Please read the
   Security Bulletin at
   http://www.microsoft.com/technet/security/bulletin/ms02-024.asp
   for information on obtaining this patch.



Relevant Pages

  • Microsoft Security Bulletin MS02-024
    ... Authentication Flaw in Windows Debugger can Lead to ... Software: Microsoft Windows ... A successful attack requires the ability to logon interactively to the ... systems and terminal servers. ...
    (microsoft.public.security)
  • [Full-disclosure] MDaemon NOT vulnerable .. sorry for the advisory.. QBik Wingate is vulnerable
    ... And it really looked like one in the debugger.. ... problem is the "vulnerability" is only ... QBik Wingate version 6.1.1.1077 Remote Buffer Overflow ...
    (Full-Disclosure)
  • Re: Big problems with 7.1 locking up :-(
    ... This is happening across several different servers, all of which are slight variants on the DL360, so I dont think it is something perculiar to me. ... If it still hangs rather than panicking, are you able to break into the debugger on the console? ... If you're using a video console and not able to get to the debugger, would it be possible to configure a serial console and use that -- serial breaks are often more successful at getting to the debugger than keyboard breaks. ...
    (freebsd-stable)
  • Re: DateTime.Now not working?
    ... since like I've said it doesn't happen with the debugger. ... In fact, it doesn't happen on my development machine, it only seems to ... happen on one of the Win2003 R1 servers. ... experiencing problems with DateTime.Now... ...
    (microsoft.public.dotnet.languages.csharp)