Closed
Bug 1009169
Opened 11 years ago
Closed 10 years ago
Invisible mouse cursor when leaving bounds of SWF over DIV and via context menu
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jordi.chancel, Unassigned)
References
Details
(Keywords: sec-low)
Attachments
(1 file, 4 obsolete files)
53.19 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release)
Build ID: 20140512030202
Steps to reproduce:
This vulnerability is more or less similar to bug995603 but it works on the fixed version (firefox nightly 32).
steps:
-1 go with the cursor on the flash object
-2 exit the flash object slowly by the up
(I think a better way for make the cursor invisible is possible , i will work for that.)
Results:
Cursor can be sometime totally invisible
Actual results:
you can make a cursor-jacking/click-jacking/spoofing attacks when the cursor in totally invisible.
Expected results:
when you exit the flash object by the up slowly the cursor can be totally invisible.
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Comment 1•11 years ago
|
||
youtube private video => https://www.youtube.com/watch?v=52A0Ov3KBuE&feature=youtu.be
Comment 2•11 years ago
|
||
It is pretty difficult to reproduce, but eventually I can see it. As is, hard to exploit.
Reporter | ||
Comment 3•11 years ago
|
||
I will works on it for make this more easy to exploit.
Reporter | ||
Comment 4•11 years ago
|
||
I have found a way for make sure than the cursor will be invisible but it's needed to right click and go to the context menu...
do you want view this?
![]() |
||
Updated•11 years ago
|
Summary: Firefox for MAC - mouse can be totally invisible when you exit a flash object slowly by the up → mouse can be made invisible when exiting a flash object slowly moving up
Reporter | ||
Updated•11 years ago
|
Summary: mouse can be made invisible when exiting a flash object slowly moving up → mouse can be made invisible when exiting a flash object slowly moving up OR make a right click and move the mouse on the flash object and go to the context menu.
Reporter | ||
Comment 5•11 years ago
|
||
video with right click => https://www.youtube.com/watch?v=O_gS9S_kQRI&feature=youtu.be
So I can repro this as well, I noticed that the "phantom" pointer has an upper bound of the bottom of the flash object (but that may be because I am hitting the upper limit of the OS windows with the actual invisible pointer) and that if I re-navigate over the flash object my real pointer re-appears.
Is this a regression or a case that just got missed instead of fixed?
in the context menu object case the mouse can be restored by the "esc" key
Summary: mouse can be made invisible when exiting a flash object slowly moving up OR make a right click and move the mouse on the flash object and go to the context menu. → mouse can be made invisible when exiting a flash object slowly moving up or by opening the context menu on object
I also got the pointer back by navigating to the edge of my screen in the context menu case
![]() |
||
Updated•11 years ago
|
Summary: mouse can be made invisible when exiting a flash object slowly moving up or by opening the context menu on object → mouse can be made invisible when exiting a flash object slowly moving up or by opening the context menu the flash object
Reporter | ||
Comment 9•11 years ago
|
||
I have found a new way for make the cursor totally invisible. I use WebRTC and when i move the mouse on the flash object , the webRTC prompt will cover the flash object and the cursor will be totally invisible!
I will upload the new testcase now.
Reporter | ||
Comment 10•11 years ago
|
||
This TESTCASE use WebRTC , when you move the mouse on the flash object , the WebRTC prompt will cover it and the cursor will be totally invisible.
Attachment #8421215 -
Attachment is obsolete: true
Reporter | ||
Comment 11•11 years ago
|
||
This TESTCASE is an update of TESTCASE 2 and is more exploitable.
Please don't use testcase2 and use this TESTCASE N°3 .
Attachment #8421273 -
Attachment is obsolete: true
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Summary: mouse can be made invisible when exiting a flash object slowly moving up or by opening the context menu the flash object → mouse can be made invisible WHEN THE WEBRTC PROMPT COVER THE FLASH OBJECT or exiting a flash object slowly moving up or by opening the context menu the flash object
Reporter | ||
Comment 12•11 years ago
|
||
This TESTCASE N°4 is an update of testcase N°3 , please use this testcase and not the testcase N°3.
Move your mouse on the flash object, wait 2s and the WebRTC Prompt will cover the flash object and the cursor will be totally invisible.
Attachment #8421275 -
Attachment is obsolete: true
Reporter | ||
Comment 13•11 years ago
|
||
An Example with WebRTC prompt (more critical).
Reporter | ||
Comment 14•11 years ago
|
||
Youtube private Video with WebRTC prompt => https://www.youtube.com/watch?v=DYSiHhbMqWs&feature=youtu.be
Comment 15•11 years ago
|
||
The original bug here and the new bug in comment 12 are very different. The first one is an edge case related to bug 995603 that should be fixed, but is not as serious. The second one involves spawning the WebRTC dialog while the Flash movie has hidden the cursor.
I believe the first bug - the original bug - is a pretty low rating. However, the second one is bad. Looks trivial to clickjack the WebRTC permission dialog. I strongly feel that we need to always force the mouse cursor to be displayed whenever that dialog is shown.
Updated•11 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 16•11 years ago
|
||
I am renaming this bug and splitting off the WebRTC issue into its own issue - bug 1009540. Please move conversation of that issue to that page.
This bug will remain open to deal with the edge cases of slowly leaving the SWF bounds overlapped by a DIV (bug 995603) and the context menu.
These bugs should be rated separately.
Summary: mouse can be made invisible WHEN THE WEBRTC PROMPT COVER THE FLASH OBJECT or exiting a flash object slowly moving up or by opening the context menu the flash object → Invisible mouse cursor when leaving bounds of SWF over DIV and via context menu
Reporter | ||
Comment 17•11 years ago
|
||
- "Invisible mouse cursor when leaving bounds of SWF over DIV" : I would to say that it's not needed to leaving bounds of SWF over DIV. You can just go out bounds (up and not down) of SWF and just go on the <body>, or others objects (as you want) But not necessarily DIV.
Flags: needinfo?(mwobensmith)
Flags: needinfo?(curtisk)
Reporter | ||
Comment 18•11 years ago
|
||
- And i would to say that it is not necessary too to go out slowly but sometime with a normal speed the mouse can be totally invisible as well.
![]() |
||
Updated•11 years ago
|
Flags: needinfo?(curtisk)
Updated•11 years ago
|
Flags: needinfo?(mwobensmith)
Reporter | ||
Comment 19•11 years ago
|
||
(In reply to Jordi Chancel from comment #17)
> - "Invisible mouse cursor when leaving bounds of SWF over DIV" : I would to
> say that it's not needed to leaving bounds of SWF over DIV. You can just go
> out bounds (up and not down) of SWF and just go on the <body>, or others
> objects (as you want) But not necessarily DIV.
- Can you fixed the title of this bug please?
We believe the title of the bug is sufficiently accurate and that the comments provide any further necessary information.
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Attachment #8421538 -
Attachment is obsolete: true
Comment 21•10 years ago
|
||
Since this issue fixes (as much as anything) bug 1009540 as well this, is there a way to get this addressed? Is this something you could work on, Gavin?
Flags: needinfo?(gavin.sharp)
Comment 22•10 years ago
|
||
No. Sounds like some strange issue with the Flash plugin. Maybe Benjamin has some ideas.
Flags: needinfo?(gavin.sharp) → needinfo?(benjamin)
Comment 23•10 years ago
|
||
ISTR another bug like this one (mac-specific), but I can't remember it. Flash is setting the mouse cursor and isn't resetting it properly. smichaud, do you remember a bug like this?
In either case, can we do something simple like force reset/show the mouse cursor when the mouse leaves a plugin?
Component: General → Plug-ins
Flags: needinfo?(benjamin) → needinfo?(smichaud)
Comment 24•10 years ago
|
||
It will take me a while to look into this.
> In either case, can we do something simple like force reset/show the
> mouse cursor when the mouse leaves a plugin?
I think we already do. It's possible, though, that there are still
some cases where a mouse-exit event isn't sent where it's supposed to
be.
Comment 25•10 years ago
|
||
> ISTR another bug like this one (mac-specific)
You're probably thinking of bug 995603.
Among other things, I need to check that the patch for bug 1092630 didn't regress the fix for that bug.
Comment 26•10 years ago
|
||
From re-reading the comments, I understand this bug is very difficult to reproduce. And given the number of testcases, it's not clear we don't have more than one bug here.
It may be better to concentrate on bug 1009540, which (apparently) effects all platforms and seems a bit more definite.
I will double-check that the fix for bug 995603 hasn't been regressed by the patch for bug 1092630. But beyond that there's probably nothing we can do here.
Flags: needinfo?(smichaud)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Updated•9 years ago
|
Group: core-security → core-security-release
Updated•5 years ago
|
Group: core-security-release
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•