More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Patch-Diff Analysis: Read the Fix, Rebuild the Bug

    1

    Turn a vendor patch into an understood vulnerability — diff before/after binaries, read the fix to infer the bug class, build a minimal PoC, verify both builds.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Patch-Diff Analysis: Read the Fix, Rebuild the Bug

    Patch-Diff Analysis: Read the Fix, Rebuild the Bug

    Example session with this skill installed

    A Patch Tuesday advisory describes a kernel driver race with no PoC. Diff the patched and unpatched builds, infer the bug, and prove the patch works.

    • Read your context and instructions
    • Compiled the patch-diff analysis

    Pulled the pre- and post-patch driver builds from the same toolchain — matching versions matter, because different compilers drown the real change in noise. ghidriff flagged one function at 0.72 similarity: the gold is in the middle range, same function with changed logic, while near-1.0 functions are untouched and near-0.0 are refactors. Read the fix: the new code adds a spinlock acquisition plus a reference-count check before object use. The confession is unprotected object lifetime — a classic double-free race. PoC matched to the class: two threads, one closing the handle in a loop, one issuing the IOCTL in a loop, to widen the window the lock now closes. Minimal by design — the smallest input that demonstrates the bug. Verification, in order: unpatched build bugchecks within a minute, reliably, not once-in-twenty. Patched build runs the same PoC clean for an hour. Patched sanity: the component's normal function still works — a fix that bricks the IOCTL is not a fix. Report documents the diff evidence, the inferred class, the PoC, both-build verification, and the scope authorization. The vendor's patch is confirmed effective — which is itself a useful finding to hand back. The analysis is done when both builds agree: one crashes, one does not.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    When a vendor ships a security patch, the diff between the old and new binary is a signed confession: here is exactly what was wrong. This skill turns that confession into understanding — what the bug was, how it triggered, and a proof-of-concept that demonstrates it. It covers getting both binaries from the same toolchain, diffing at function granularity with BinDiff, Diaphora, or ghidriff, reading the added code to infer the bug class from the fix shape, writing a minimal PoC matched to that class, and verifying on both builds — plus the boundaries that keep it authorized testing: bug-bounty scope, SRC engagement, or your own lab.

    A patch sometimes adds a mitigation rather than fixing the root cause, and sometimes closes one trigger path while the bug remains reachable elsewhere — the skill teaches you to note which one you are looking at.
    A PoC proves the trigger, not full exploitability; weaponization is a separate, larger question.
    Diffing builds from different compilers or optimization levels drowns the real change in noise — matching versions is a precondition, not a nicety.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    No. 'The patch is public' does not authorize testing against other people's unpatched systems. Authorized targets only: your own VMs, a bounty with explicit scope, or an SRC engagement.

    Your PoC is wrong or the environment is. A PoC that crashes both proves nothing about the bug — go back to reading the fix.

    Maybe not. A mitigation is not a root-cause fix. Note which one you are looking at and check whether the bug is still reachable by another path.

    New in Security