restler
Auth/lab ref: Stateful REST API fuzzer from OpenAPI specs. For testing complex API dependency chains, producer-consumer request sequencing, and replayable bug-bucket workflows for API reliability/security testing.
v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 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/restlerScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto5ca93d77…5f6c3e2d
5ca93d771b72…bb4d5f6c3e2d1 file · 1.5 KBScansioneBasso1 segnalazione
- Link a domini esterni
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/restler@21cd568
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
RESTler explores deeper API states by inferring request dependencies from OpenAPI definitions.
Workflow (Recommended Order)
- Compile: OpenAPI -> RESTler grammar.
- Test (smoke): verify setup and required dictionary values.
- Fuzz-lean: quick bug hunting baseline.
- Fuzz: deep BFS-style state exploration.
Quick Start
# Build (local)
python build-restler.py --dest_dir <restler_bin>
# Typical campaign starts with compile + test before fuzz modes
restler.exe fuzz-lean --grammar_file <grammar.py> --dictionary_file <dict.json>
restler.exe fuzz --grammar_file <grammar.py> --dictionary_file <dict.json> --time_budget 1Operator Flow
- Validate schema quality and authentication path first.
- Run
test/smoke style workflow to confirm dependencies and dictionary values. - Run
fuzz-leanfor quick risk discovery. - Run
fuzzfor deeper sequence exploration with settings file tuning. - Reproduce via replay logs and bug buckets before assigning fixes.
Practical Notes
- Always fix setup gaps discovered in
testmode before deep fuzzing. - Deep fuzzing can cause service instability/outages on weak implementations.
- Use replay logs and bug buckets for deterministic re-validation.
High-Value Settings
fuzzing_mode(bfs,bfs-cheap,random-walk,directed-smoke-test)max_sequence_length,max_combinations- include/exclude endpoint filters (
include_requests,exclude_requests,path_regex) - retry & timing controls (
custom_retry_settings,producer_timing_delay) - trace database (
use_trace_database) for structured replay workflows
Replay & Triage Pattern
- Start from
bug_buckets.txtsummary. - Open specific bucket replay log and verify request sequence.
- Replay with same auth/host settings.
- Confirm reproducibility and collect minimal sequence evidence.
- Patch server + rerun replay to verify closure.
Common Pitfalls
- Skipping auth refresh handling leads to noisy false negatives.
- Fuzzing full API surface without scope controls can burn time-budget quickly.
- Forgetting manual cleanup after replay-created resources.
Resources
- https://github.com/microsoft/restler-fuzzer
- https://github.com/microsoft/rest-api-fuzz-testing
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/Fuzzing.md
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/SettingsFile.md
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/BugBuckets.md
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/Replay.md
File di questa versione
- SKILL.md3.0 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | Sì | Sì |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 5ca93d77 | Firmata | – |
Altro da AeonDave
Tutto da questo editoreAltro in Reverse engineering e fuzzing
Vai alla categoriaChiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login