checksec
Auth/lab ref: Linux binary and kernel hardening inspection tool for RELRO, canary, NX, PIE, RPATH, RUNPATH, symbols, fortify, and kernel config checks.
v2026.11.13-21cd5683 installs+3 in 7 days39 Starssynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/checksecWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagea0e6366a…8d6c5ccc
a0e6366acd05…edb88d6c5ccc1 file · 1.4 KBScanMedium1 finding
- No license found
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/checksec@21cd568
On this page
Quick hardening triage for ELF binaries and Linux kernels.
When to use checksec
Use checksec when you need to answer questions like:
- Is PIE enabled?
- Is there a stack canary?
- Is NX enforced?
- Is RELRO partial or full?
- Are symbols stripped?
- What kernel hardening settings are enabled?
This is often the first command in pwn/reversing triage.
Quick Start
# Inspect one binary
checksec file /bin/ls
# JSON output for automation
checksec file /bin/ls --output json
# Kernel hardening survey
checksec kernelOutput Modes
checksec file ./target --output cli
checksec file ./target --output json
checksec file ./target --output yaml
checksec file ./target --output xmlUse machine-readable output when feeding exploit notes, parsers, or dashboards.
Common Workflows
Pwn triage
checksec file ./vulnInterpret quickly:
- No PIE → static code addresses stay stable
- No canary → stack overflow path is simpler
- NX enabled → likely ret2libc/ROP instead of raw stack shellcode
- Partial RELRO → GOT overwrite may still be viable
Batch or scripted inspection
checksec file ./target --output jsonKernel review
checksec kernel
checksec kernel --output jsonUseful for local privesc context or hardening audits.
Fortify-focused check
checksec fortifyProc 1Use when you want deeper fortify coverage rather than just the summary row in normal binary output.
Cross-Compiled / Offline Filesystem Use
Upstream notes two important limits:
- kernel checks must run on the live system you actually want to assess
- file checks work offline except fortify may need the target libc context
For offline target filesystems, consider pairing checksec with native readelf if the environment is stripped down.
Practical Notes
- Current upstream has moved toward a Go implementation and is faster than the old bash-heavy workflow.
- Checksec is a triage tool, not a full exploitability oracle.
- Always pair the result with real reversing:
readelf,objdump, debugger output, and vulnerability context.
Caveats
- A "hardened" binary can still be exploitable.
- A missing mitigation does not guarantee an easy exploit.
- On non-Linux hosts some checks are limited.
Resources
No bundled scripts/, references/, or assets/.
Use upstream examples for the latest subcommands and output schema.
Files in this version
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumLicense · No license found
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.11.13-21cd568 | Nov 13, 2026 | 21cd568 | a0e6366a | Signed | – |
More from AeonDave
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