aeondave/one-gadget
offensive-tools/rev/one-gadget/SKILL.md
one-gadget: libc gadget finder for `execve`-style code execution opportunities under known register and stack constraints. Use when you already have a libc leak or version match and want candidate single-shot RCE offsets to test before building a longer ROP chain.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill one-gadgetInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 4:56 AM161.0s1 file scanned
SKILL.md
- name:
- one-gadget
- description:
- one-gadget: libc gadget finder for `execve`-style code execution opportunities under known register and stack constraints. Use when you already have a libc leak or version match and want candidate single-shot RCE offsets to test before building a longer ROP chain.
- compatibility:
- Linux and macOS host; Ruby gem; targets glibc-style libc binaries
- author:
- AeonDave
- version:
- 1.0
one-gadget
Fast libc post-leak shortcut finder. Great when it works, humbling when constraints bite back.
When to use one-gadget
Use one-gadget when you need to:
- turn a libc base leak into candidate
execveoffsets - compare several constraint-heavy RCE options quickly
- decide whether a short stack/register fix-up beats a full custom chain
Quick Start
# Enumerate candidate gadgets in libc
one_gadget ./libc.so.6
# Show more gadgets and constraints
one_gadget -l 2 ./libc.so.6
# Raw offsets only
one_gadget --raw ./libc.so.6
Practical Workflow
- Identify the exact libc or a trustworthy build match.
- Compute the libc base from your leak.
- Run
one_gadgeton that libc file. - Read the printed constraints carefully.
- Validate stack, registers, and writable memory in
gdbbefore betting the exploit on one offset.
Practical Notes
- Constraints are the whole game:
rspcontents,rax == NULL, or writable memory requirements often decide feasibility. one-gadgetis best after you already solved ASLR for libc.- Keep a normal ROP fallback path ready; many stable exploits start with
one-gadgetas a probe, not as the final design.
Caveats
- A valid offset does not imply a reachable or repeatable exploit path.
- Version drift between local and remote libc makes results meaningless.
- CET, seccomp, stack layout differences, or register clobbers often kill the magical one-shot path.
Resources
No bundled scripts/, references/, or assets/.
Use the upstream gem README for installation, constraint-depth controls, and supported libc assumptions.
Related Skills
aeondave/offensive-linux-role
data-ai
VerifiedTrustedCommunity
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
4SKILL.mdUpdated Jun 5, 2026
aeondave/ics-technique
development
VerifiedTrustedCommunity
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
4SKILL.mdUpdated Jun 2, 2026
aeondave/game-technique
tools
VerifiedTrustedCommunity
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
4SKILL.mdUpdated Jun 2, 2026
aeondave/hardware-technique
development
VerifiedTrustedCommunity
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
4SKILL.mdUpdated Jun 2, 2026