Authentication Flaw in Windows Debugger.
Results 1 to 2 of 2

Thread: Authentication Flaw in Windows Debugger.

  1. #1
    Senior Member
    Join Date
    Nov 2001

    Authentication Flaw in Windows Debugger.

    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:
    - ----------------------------------------------------------------------


    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
    for information on obtaining this patch.

  2. #2
    Senior Member
    Join Date
    Nov 2001
    Yep, Microsoft's at it again...
    Chris Shepherd
    The Nelson-Shepherd cutoff: The point at which you realise someone is an idiot while trying to help them.
    \"Well as far as the spelling, I speak fluently both your native languages. Do you even can try spell mine ?\" -- Failed Insult
    Is your whole family retarded, or did they just catch it from you?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts