exploit-chaining
Combine low/medium findings into one high-impact exploit chain, and amplify demonstrated impact. Load when you have several small bugs, a "so what?" finding, on "chain", "escalate impact", or building the narrative for a report. Signals: self-XSS + CSRF, open-redirect + OAuth, IDOR + info-leak, SSRF
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/exploit-chainingScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto820a85ab…59396687
820a85ab3d5c…6c2d593966871 file · 1.4 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/exploit-dev/exploit-chaining@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
You have bugs that are individually "meh" (self-XSS, an info leak, an open redirect, a weak CSRF) and need to turn them into something a program pays for — or a pentest foothold that needs several bugs stacked.
Why it works
Impact is compositional. One bug supplies a precondition another needs: a leak provides the id IDOR needs; an open redirect makes OAuth leak a token; SSRF reaches the metadata service that yields cloud creds. The chain's severity is the end impact, not the weakest link.
Method
- Inventory every finding with what it gives and what it needs (primitive in / out).
- Look for matches: does bug A's output satisfy bug B's precondition? Common chains:
- self-XSS + login-CSRF / cookie-fixation → land XSS in the victim's session.
- open redirect + OAuth
redirect_uri→ steal the authorization code → ATO. - IDOR/info-leak → user id/UUID → BOLA on another endpoint.
- SSRF →
cloud-imds-ssrf→ IAM creds → cloud impact. - file upload (stored) → XSS/SSRF/RCE depending on how it's served.
- Build the shortest reliable path to the highest impact; script the PoC end-to-end.
- Write the narrative: state the end impact first, then each link with its role, so a
triager sees severity immediately (see
reporting-bug-bounty-writeup).
Gotchas
- Don't over-chain — the simplest path to real impact is more credible and reproducible.
- Each link must be reliable; a flaky step sinks the whole chain in triage.
- Keep every step in scope and within RoE — a chain that steps out of scope is unreportable.
Verify success
A single reproducible PoC that starts from attacker-controlled input and ends at concrete high impact (ATO, data access, RCE, cloud takeover).
References
Bug-bounty disclosed chains (HackerOne Hacktivity); PortSwigger chained-attack labs.
File di questa versione
- SKILL.md2.4 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
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.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 820a85ab | Firmata | – |
Altro da NoorQureshi
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