DLL_Version_Enumeration_BOF
What is this?
This is a
Cobalt StrikeBOFfile (a mildly massaged port of @N4k3dTurtl3's existing PoC , meant to use ascertain information regarded importedDLLs(via theENTRY_RESOURCE) within current process that your beacon associated with.
What problem are you trying to solve?
Given my current projects regarding
DLLs, this is yet another blindspot I wanted to address after seeing @N4k3dTurtl3's work.I wanted to support both
32-bitAND64-bitBeaconsessions.I wanted to have verbose or minified output, given an operator's desire
I wanted to keep the original design of @N4k3dTurtl3's intact; minimal API calls.
This is solved this by rolling our own from
groked orcribbedimplementations elsewhere.
How do I build this?
In this case, you have two options:
Use the existing, compiled object file, located in the
distdirectory (AKA proceed to major step two)Compile from source via the
Makefilecd srcmake cleanmake
Load the
Aggressorfile, in theScript Manager, located in thedistdirectory
How do I use this?
From a given
Beacon:

Any known downsides?
We're still using the
Win32API andDynamic Function Resolution. This is for you to determine as far as "risk", though this is limited to a single comparison function (stricmp).You may attempt to incur a privileged action without sufficient requisite permissions. I can't keep you from burning your hand.
What does the output look like?
All known DLLs associated with the process
DLLs associated with the process
Verbose output of the aforementioned

Verbose output of the aforementioned with needle
needle
Last updated