Dll Interceptor should write nop instructions to the remaining bytes of the final instruction
Categories
(Core :: mozglue, defect)
Tracking
()
People
(Reporter: gstoll, Assigned: gstoll)
References
Details
Attachments
(1 file)
The WindowsDllDetourPatcher overwrites the first 13 (or 10) bytes of a function with a jump to a patched function. If the 13 bytes ends in the middle of an instruction, it leaves the rest of the bytes of that instruction alone, which can cause problems if something else wants to detour that function later. We should instead overwrite the rest of the bytes in that instruction with nop
. (or int 3
, I suppose)
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:glandium, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Assignee | ||
Comment 2•1 year ago
|
||
In bug 1833793 we discovered that ESET is indeed hooking some of the functions that we do after us. I don't think that this is causing them problems right now, but to be on the safe side I'd like to fix this.
Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Comment 5•1 year ago
|
||
bugherder |
Comment 6•1 year ago
|
||
Is this something we should consider backporting anywhere?
Assignee | ||
Comment 7•1 year ago
|
||
Probably not. We don't know of any problems it's causing - well-behaved things that are detouring the functions that we detour should handle this case correctly. And it is a little risky.
Description
•