Menu

Individual skill

performing-windows-binary-exploitation

0upvotes

Methodology for exploiting classic 32-bit Windows stack buffer overflows in network services during authorized engagements (OSCP-level), covering crash reproduction, EIP offset discovery with pattern_create/pattern_offset, shellcode space and bad-character enumeration, locating a reliable JMP ESP return address with mona.py, and delivering an msfvenom payload to gain remote code execution.

internal/tools/skills/data/binary-exploitation/performing-windows-binary-exploitation/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,329
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performing Windows Binary Exploitation

## When to Use

- During authorized assessments or OSCP-style labs against a 32-bit Windows network service (e.g., SLMail POP3, custom
  TCP daemons) that crashes when sent an oversized request to a field such as `USER`, `PASS`, or a protocol command.
- When you have a Windows debugger (Immunity Debugger + mona.py, or x32dbg/WinDbg) attached and can observe that a large
  input overwrites `EIP`, indicating a saved-return-address overwrite.
- When the target binary/DLLs lack modern mitigations (no ASLR, no DEP/NXCompat, no SafeSEH) so a static `JMP ESP`
  return address into stack-resident shellcode is viable.
- As the end-to-end recipe to take a crash from proof-of-concept DoS to a working reverse/bind shell.

## Critical: Concepts/Steps Most Often Missed
Back to top