bypassuac_injection needs updating due to changes in Windows 10

[OJ]

The bypassuac_injection module currently doesn't work on Windows 10 (as of a recent update). MS have patched this vector. We need to update the module so that Windows 10 versions that are new enough are no longer marked as pwnable. Either that or we spend some time adding a new vector that is known to work.

At this point, I think just adding a version check is good enough, because the bypassuac_eventvwr module works just fine.

Adding this as a reminder for myself more than anything (and will self-assign).

[ATrashInTheWorld]

So, I don't know what kind of update there is need to be, but is it related to to the fact that when I use this exploit it kills my multi/handler session?

[OJ]

Nope. This is something else.

Soon, the comhijack method will be landed, and that works well on all versions.

[ATrashInTheWorld]

Then, without being a nuisance, would you be able to tell me where I could find a solution or an explanation of this inconvenient, please.

You're actually the only one who answered me up until now.

[OJ]

I have no idea what your problem is, so I'm not really able to say what the solution is.

[ATrashInTheWorld]

Alright, thank you.
Good luck in your work.

[ATrashInTheWorld]

Hello, I just came back to ask, by curiosity, how are things going?
Also, could you send me a link on how to use bypassuac_eventvwr when you have some free time?

[OJ]

Try the new com hijack module that got landed recently instead.

…

On Aug 21, 2017 07:23, "ATrashInTheWorld" ***@***.***> wrote: Hello, I just came back to ask, by curiosity, how are things going? Also, could you send me a link on how to use bypassuac_eventvwr when you have some free time? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#7673 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABw4P7cZCFpKWllXEcotUVTllcmQ7Oqks5saKPCgaJpZM4LHRJM> .

[github-actions]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.