Re: xp remote desktop bluescreen or how to shoot your pc

Tech-Archive recommends: Speed Up your PC by fixing your registry

On Sun, 5 Jul 2009 18:24:07 -0500, "Shenan Stanley"
<newshelper@xxxxxxxxx> wrote:

techsc wrote:
- i have posted this bug report more than one year ago already -

Windows XP Pro En SP3 Remote Desktop Blue Screen Procedure:

Here comes the procedure to reproduce a severe bug in the windows xp
terminal service (RDPDD.dll):

Set up a windows xp pro host and connect then from a remote
computer via remote desktop.

1)
connect and logon (create new session) at color depth 15bit

2)
disconnect (leave the user logged on)

3)
connect and logon to the created session at color depth 16bit

4)
disconnect

5)
connect and logon to the created sesseion at color despth 15bit

-> voila, the remote desktop host system reboots!

- I can reproduce this bug on all 4 availble computers (all xp pro
with sp3) at my location.

Shenan Stanley wrote:
ATI video cards?

techsc wrote:
The bug is not related to any video card. I can reproduce the bsod
on ati, nvidia and even on vmware virtual machine cards. Anyone can
try it.

It's Windows XP - it's pretty much a dead horse.
A year ago - it was actually pretty much a dead horse. ;-)

Not to mention - I am unsure why anyone would do what you specify - and I am
just meaning connecting at such a low color depth, much less this change
from low to slightly higher back to low.


Not very constructive. The fact it is reproducible across a variety of
platforms is cause enough for concern. XP is far from dead, since MS
has yet to produce a newer system in sufficient population and appeal
to supplant all the installed XP boxes, it should still be on the
table for a fix. It's a bug that should have been detected and fixed
by now. The bug is reproducible on my Dell laptops and HP desktops.

If this scenario, or something like it, can be shown to kill a machine
during the connect process without needing a valid login it would make
for a fine denial of service attack. Since the code base for RDP is
probably close to if not identical to Terminal Services it could be
used to take down a TS box. It demonstrates a potential vulnerability
that could be exploited as a DoS or, with the proper frames, a way
into a kernel driver for elevation of privilege.

To techsc: this is not a proper place for a bug report in any case.
This should be submitted to the Microsoft support team as a proper bug
report, not in the newsgroups. You won't get much action from MS by
posting here, as you have demonstrated.
.

Relevant Pages

  • Re: xp remote desktop bluescreen or how to shoot your pc
    ... The bug is not related to any video card. ... Windows XP Pro En SP3 Remote Desktop Blue Screen Procedure: ... Here comes the procedure to reproduce a severe bug in the windows xp ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: the remote computer has ended the connection
    ... If you believe that it is a bug within Windows, ... you should ring the Microsoft Helpdesk in your country ... the users who are authorised to use Remote Desktop. ...
    (microsoft.public.windowsxp.general)
  • Re: xp remote desktop bluescreen or how to shoot your pc
    ... Windows XP Pro En SP3 Remote Desktop Blue Screen Procedure: ... Here comes the procedure to reproduce a severe bug in the windows xp ... connect and logon to the created session at color depth 16bit ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Java and avoiding software piracy?
    ... reproduce your bug on my WinXP SP2 machine. ... Windows crap myself, I also couldn't verify these tricks. ... really likes the taste of sushi, but doesn't know the supposedly intricate ...
    (comp.lang.java.programmer)
  • Re: DataGrid ReadOnly Column BUG !
    ... Have you reproduce the bug on a Windows XP pro machine with SP2? ... SP1 seems to be automatically installed when installing ...
    (microsoft.public.dotnet.framework.windowsforms)