CVE-2016-10555 PoC — jwt-simple 安全漏洞

Source

https://github.com/CircuitSoul/poc-cve-2016-10555

Associated Vulnerability

Title:jwt-simple 安全漏洞 (CVE-2016-10555)
Description:Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants.

Description

Change the algorithm RS256(asymmetric) to HS256(symmetric) - POC (CVE-2016-10555)

Readme

# Change the algorithm RS256(asymmetric) to HS256(symmetric) - POC (CVE-2016-10555)

The algorithm HS256 uses the secret key to sign and verify each message.
The algorithm RS256 uses the private key to sign the message and uses the public key for authentication.

If you change the algorithm from RS256 to HS256, the back end code uses the public key as the secret key and then uses the HS256 algorithm to verify the signature.


Regards:
https://www.youtube.com/c/FarahHawa

File Snapshot


 [4.0K]  /data/pocs/df230e2b3a73beb05b865f8719ffaa2756fa3cbd
├── [ 773]  jwt-hs256-with-publickey.py
├── [ 800]  public_key.pem
└── [ 475]  README.md

0 directories, 3 files

Shenlong Bot has cached this for you

Remarks

1. It is advised to access via the original source first.

2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.

View subscription plans →

Goal Reached Thanks to every supporter — we hit 100%!