Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
POC_CVE-2015-9235 — Demo of the algorithm confusion attack on various JWT libraries | Kitploit
Tools/GitHubGitHub/tierchampion/poc_cve-2015-9235
Vulnerability AnalysisExploitationWeb Application ExploitationCTFAuthenticationLearning & Education
GitHubtierchampion/poc_cve-2015-9235

POC_CVE-2015-9235

Demo of the algorithm confusion attack on various JWT libraries

View Repository
308 months agoNot yet reviewed
Share

CVE-2015-9235

Demonstration of the algorithm confusion attack on Json Web Token (JWT) libraries. JWTs are often used in cookies to certify a user session and so this attack is critical. The node module [email protected] was used to demonstrate the vulnerability.

This project was also a nice vibe coding activity as the front end was almost entirely done with LLMs outside of the api calls.

Vulnerability

The format of a JWT is the following:

b64(header).b64(payload).b64(signature)
With in our case:
  header = (algorithm, type)
  payload = (username, role)

At the time, the various JWT libraries could sign with an algorithm, but didn't enforce an algorithm and rather relied on the content of the header of the JWT, thus letting the user decide its own encryption. This allows for many exploits, but the one used in this case is the following:

  1. Backend creates JWTs with an RSA 256 signature using its private key
  2. Attacker fetches the public key from the backend, which is a perfectly normal use case
  3. Attacker forges a custom JWT with a symmetric algorithm (HMAC SHA-256 in our case) using the public key as the secret while also setting the algorithm to HS256 in the header
  4. Backend verifies the JWT by doing HS256 with its public key and the token is validated!

Walkthrough

Authenticate as any user on the login page. You will need to register first.

Once on the home page, there will be a button that can only be clicked if you have a valid admin session. You will then need to run the exploit to forge this JWT.

Finally, you replace the original JWT with the forged JWT in the local storage and after a refresh, the button should be clickable and the flag is yours!

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    871
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    548
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    383
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    361
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    305
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →