Home Dashboard Directory Help
Search

Possible backdoor in Control.ReflectMessage() to send messages to any window handle by ceztko


Status: 

Resolved
 as External Help for as External


1
0
Sign in
to vote
Type: Bug
ID: 669747
Opened: 5/21/2011 12:49:56 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

(NB: actually I'm seeing this in VS 2008 SP1)

It seems that is still possible to send any message to any window handle using Control.ReflectMessage(). Just create a custom message, decrement it by WM_REFLECT, and send it with Control.ReflectMessage() in a Control inherited class. It doesn't seems there's a violation of the security policies. Still, I'd like to know if this is really supported: I like the possibility, like in .NET Compact Framework with MessageWindow class, but wouldn't like it to disappear without communications.

I found this behavior while looking for a way to forward a message to a control (in the specific case: forwarding a mouse wheel event to the control under the mouse cursor, a feature that I can't understand why but is lacking from .NET...) and couldn't find any other way than P/Invoking SendMessage or this one.
Details
Sign in to post a comment.
Posted by MS-Moderator08 [Feedback Moderator] on 5/22/2011 at 7:20 PM
Thanks for your feedback.
But now we are no longer accepting bugs for Microsoft Visual Studio 2008 and earlier products. we only support the latest Visual Studio versions for bug/suggestion.
We are therefore closing this issue. If you can reproduce the issue on VS 2010, please reactivate this issue(Click "Edit this item" button on the site and change the "Status" to "Active"). If not, you can contact
http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx
for help.
Sorry for the inconvenience.
Sign in to post a workaround.