1

DC OS - Windows Server 2008 R2 Std

Client OS - Windows XP, Windows 7

I have implemented Security policy through Network Policy Server and enabled Wired AutoConfig Services Automatically. While Enabling Wired AutoConfig Services, if i check mark on ' Allow service to interact with Desktop ' It works proper in some of Window7 Laptop.

But on internet it is giving me Warning that "Interactive services can display a user interface and receive user input. If you allow the service to interact with the desktop, any information that the service displays on the desktop will also be displayed on an interactive user's desktop. A malicious user could then take control of the service or attack it from the interactive desktop."

Can you give me some example how Malicious User can take control of the service or attack it from the interactive desktop?

3

Microsoft introduced session 0 isolation in 2008/Vista. With session zero isolation, all Windows services now run in session 0, and all human sessions run in session 1 and above.

So, it is strongly discouraged to design a Windows service that requires interaction with the desktop. It is still technically possible to design a service that interacts with the desktop, but it is strongly discouraged. It's the wrong thing to do.

When a Windows service has to interact with the desktop, the interactively logged on human's desktop will get switched to looking at session 0's desktop so that the dialog box or whatever it is that needs attention, gets attention.

Now we have a very highly-privileged account, usually Local System, displaying a dialog box to a standard user. That dialog box is running in the context of Local System. You are giving that standard user an opportunity to exploit something in that dialog box and cause it to do something in the security context of Local System. So that's where the danger is.

2

The main point here are Windows' message forwarding mechanisms which allow any process to send any message to any window within its own session. This obviously presents a security risk if one of the windows belongs to a process with elevated rights. This class of attacks has been dubbed "shatter attacks" and has been discussed in depth throughout the security scene a couple of years ago.

As the root cause is impossible to fix - most, if not all software written for Windows relies on this feature - it has been decided that the only way to deal with this issue is segmentation - everything which runs in a single user session has to be run in a single security context. Service design guidelines have been reflecting this since the late 90'ies and were discouraging GUI code running in the service's context. It has been made imperative with Windows Vista, where you simply can't let a service to interact with a user's desktop any more.

Of course, this is also valid for Windows 7 and by checking "Allow service to interact with Desktop" you are allowing the service to interact with a virtual desktop which is not seen by the user. If it fixes your service - fine, let it be. But make sure that you do not have any Windows XP machines out there as this indeed would pose the aforementioned security risk.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.