Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/checksecReverse engineering e fuzzing

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 installazioni+3 in 7 giorni39 Stellesincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/checksec

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
0N00OgGti8…qljsN6DA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettoa0e6366a…8d6c5ccc
a0e6366acd05…edb88d6c5ccc1 file · ⁦1.4 KB⁩
ScansioneMedio1 segnalazione
  • Nessuna licenza trovata
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/checksec@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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

bash
# Inspect one binary
checksec file /bin/ls

# JSON output for automation
checksec file /bin/ls --output json

# Kernel hardening survey
checksec kernel

Output Modes

bash
checksec file ./target --output cli
checksec file ./target --output json
checksec file ./target --output yaml
checksec file ./target --output xml

Use machine-readable output when feeding exploit notes, parsers, or dashboards.

Common Workflows

Pwn triage

bash
checksec file ./vuln

Interpret 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

bash
checksec file ./target --output json

Kernel review

bash
checksec kernel
checksec kernel --output json

Useful for local privesc context or hardening audits.

Fortify-focused check

bash
checksec fortifyProc 1

Use 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.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaLicenza · Nessuna licenza trovata

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd568a0e6366aFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login