checksec

Inspect ELF binary hardening and mitigation settings using the pwntools checksec CLI.

701|108|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/yv1ing/Z3r0 --skill checksec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checksec
Source: https://github.com/yv1ing/Z3r0/tree/main/sandbox/.agents/skills/checksec
Command: npx skills add https://github.com/yv1ing/Z3r0 --skill checksec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pwntools.

What problem does it solve?

Security analysts need a fast, consistent way to review which exploit mitigations (PIE, RELRO, NX, stack canaries) are enabled on ELF binaries during authorized assessments, without manually parsing headers for every file.

Core Features & Use Cases

  • Mitigation Triage: Run the pwntools-provided checksec CLI against in-scope binaries to capture hardening status as triage evidence.
  • Batch Review: Loop over build outputs and save consolidated checksec results to files for reporting instead of streaming large tables.
  • Cross-Verification: Pair results with file, readelf, and gdb to independently confirm PIE, RELRO, GNU_STACK, and loader details.
  • Use Case: During an authorized binary audit, run checksec across every compiled artifact in ./build, save the output to checksec.txt, and report each binary's protection status alongside its path and architecture.

Quick Start

Run checksec on the provided binary and report its mitigation status, architecture, and any risk-relevant observations.

Frequently Asked Questions about checksec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check ELF binary security protections with checksec?

Run checksec --file=./binary on the target ELF to list mitigations such as PIE, RELRO, NX, and stack canaries. Confirm details with file and readelf -h when the finding matters.

How do I run checksec on multiple binaries at once?

Loop over the binaries in a shell for-loop, run checksec --file on each, and append results to an output file such as checksec.txt. Report the saved file path instead of streaming large tables.

Is checksec a separate package from pwntools?

No, this workflow uses the checksec CLI bundled with the pwntools installation. Do not install a separate checksec implementation or apt package; run checksec --help or pwn checksec --help first.

Does checksec output prove a binary is exploitable?

No, checksec output is triage evidence only, not proof of exploitability. Pair it with readelf, gdb, or runtime testing before drawing conclusions about actual risk.

When should I use pwntools instead of checksec?

Use checksec only for mitigation triage on ELF binaries. Switch to the pwntools skill when you need exploit scripts, process interaction, packing, cyclic patterns, or shellcraft.