awful.systems
  • Communities
  • Create Post
  • heart
    Support Lemmy
  • search
    Search
  • Login
  • Sign Up
repostbot33@lemmy.worldB to netsec@lemmy.worldEnglish · 2 years ago

Weaponizing Windows Thread Pool APIs: Proxying DLL Loads Using I/O Completion Callbacks

fin3ss3g0d.net

external-link
message-square
0
link
fedilink
1
external-link

Weaponizing Windows Thread Pool APIs: Proxying DLL Loads Using I/O Completion Callbacks

fin3ss3g0d.net

repostbot33@lemmy.worldB to netsec@lemmy.worldEnglish · 2 years ago
message-square
0
link
fedilink
Weaponizing Windows Thread Pool APIs: Proxying DLL Loads Using I/O Completion Callbacks - fin3ss3g0d's Blog
fin3ss3g0d.net
external-link
In today's blog, we are going to be covering the topic of proxying DLL loads using the Windows thread pool API with C++/assembly. This specific example is going to use an I/O completion callback and is a complementary article for my GitHub repository here. Before we jump in, let me introduce some background information. Background
alert-triangle
You must log in or # to comment.

netsec@lemmy.world

netsec@lemmy.world

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !netsec@lemmy.world

Technical news and discussion of information security.

Rules:

  1. Be excellent to each other
  2. Keep it on topic
  3. Absolutely no PII or doxing
  4. No disclosure posts
Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 4 users / day
  • 4 users / week
  • 4 users / month
  • 30 users / 6 months
  • 1 local subscriber
  • 1.41K subscribers
  • 100 Posts
  • 8 Comments
  • Modlog
  • mods:
  • t8r@lemmy.world
  • BE: 0.19.12
  • Modlog
  • Instances
  • Docs
  • Code
  • join-lemmy.org