exploit-memory-corruption
Turn a memory-corruption bug in a native binary into code execution — stack overflows, format strings, and ROP against modern mitigations. Load when you control input to a compiled program and it crashes or misbehaves: a network daemon, a thick client, a setuid/SUID helper, or extracted firmware. Si
v2026.10.14-ee0e0c52 installs+2 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/exploit-memory-corruptionWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagec8d4ac9f…2019f550
c8d4ac9fc80d…53972019f5501 file · 2.1 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/exploit-dev/exploit-memory-corruption@ee0e0c5
On this page
When it applies
You have a native binary or service on an authorized target that mishandles your input — a
network-facing daemon, a thick-client, a setuid helper found during privesc, or a binary carved
from firmware (reverse-eng-firmware). reverse-eng-binary-triage located the bug; this skill turns
that crash into controlled execution. Pentest-only — this is destructive and can crash the service.
Why it works
C/C++ has no memory safety: writing past a buffer overwrites saved return addresses and pointers, and a user-controlled format string reads/writes arbitrary memory. Redirect execution to your code or to existing code (ROP) and the process does your bidding. Modern mitigations (NX, ASLR, PIE, stack canaries) don't remove the bug — they shape the technique.
Method
- Check protections first —
checksec ./bin(orpwntools): NX, PIE, RELRO, canary. This decides everything. No canary + NX → ROP; PIE → you need a leak; no PIE, no NX → maybe shellcode. - Find the offset — send a cyclic pattern (
cyclic 200/ pattern_create), crash it undergdb+GEF/pwndbg, read the value in$rip/$eip, andcyclic -l <value>for the exact offset to the saved return address. - Pick the primitive by protections:
- ret2win — a target function already in the binary; overwrite the return address with it.
- ret2libc / ROP — with NX, chain gadgets: leak a libc address (call
puts(puts@got)via the PLT), compute the libc base, return tosystem("/bin/sh")or aone_gadget. Build gadgets withROPgadget/ropper, the chain withpwntoolsROP(). - Format string (
printf(user)) — leak stack/canary/PIE base with%p, then do arbitrary writes with%n(GOT overwrite → redirect a call tosystem).fmtstr_payloadautomates it.
- Defeat mitigations with leaks — ASLR/PIE need a leaked address (from a format string or an info-leak bug) to rebase; a stack canary must be leaked (or brute-forced byte-by-byte on a forking server) and replayed in your overflow so the check passes.
- Build it with pwntools — a repeatable script:
process()/remote(),recvuntil, pack withp64(), stage the leak, then send the final chain; iterate locally, then fire at the target. - Land a shell — reuse
payloads-reverse-shellsfor what to run once you have execution.
Gotchas
- Match the exact libc — remote exploitation fails on the wrong libc version/offsets; identify it
(leaked addresses → a libc-database lookup) before computing
system/one_gadget. - Bad bytes —
\x00,\x0a,\x20can truncate input depending on the read function; check and avoid them in addresses/payload. - Local works, remote doesn't — environment/stack alignment differs; the
movapsalignment crash beforesystemis fixed by an extraretgadget. - This crashes the target — it's inherently disruptive; only on authorized pentest targets, never a live bug-bounty production service, and note the risk in the RoE.
Verify success
Reliable control of execution demonstrated on the target — a returned shell, a run command, or a
controlled $rip with a working ROP chain — reproducible from your pwntools script.
References
pwntools docs & tutorials; checksec; GEF/pwndbg; ROPgadget/ropper; one_gadget; libc-database.
Find the bug with reverse-eng-binary-triage; shell payloads in payloads-reverse-shells.
Files in this version
- SKILL.md4.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | c8d4ac9f | Signed | – |
More from NoorQureshi
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login