agentleFS
Sign inStart free
NoorQureshiNoorQureshi/security-skills/skills/exploit-dev/exploit-chaining/SKILL.md

exploit-chaining

Skill27 starsChanged 31 days agoMITView on GitHub

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 + metadata.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't over-chain — the simplest path to real impact is more credible and reproducible.

    line 42
  2. Distinctive:

    Keep every step in scope and within RoE — a chain that steps out of scope is unreportable.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Exploit chaining & impact amplification

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

  1. Inventory every finding with what it gives and what it needs (primitive in / out).
  2. 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.
  3. Build the shortest reliable path to the highest impact; script the PoC end-to-end.
  4. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free