Skip to content

Commit

Permalink
Update README.
Browse files Browse the repository at this point in the history
  • Loading branch information
DolphFlynn committed Jan 1, 2025
1 parent 33f764e commit 1fa506d
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@ Additionally it facilitates several well-known attacks against JWT implementatio

## Changelog

**Unreleased**
- Add ability to test for HMAC signatures using [weak secrets](https://github.com/wallarm/jwt-secrets).
- Remember last used key within Signing dialog.

**2.4 2024-12-24**
- Add support for non-JSON claims within JWS (Thanks to [@Hannah-PortSwigger](https://github.com/Hannah-PortSwigger) for suggesting this).

Expand Down Expand Up @@ -150,6 +154,7 @@ The `Attack` option implements several well-known attacks against JSON Web Signa
* Signing with an empty HMAC key
* Signing with a *Psychic signature*
* Embedding a Collaborator payload
* Weak HMAC secret

These are described in more detail [below](#Attacks).

Expand Down Expand Up @@ -218,6 +223,9 @@ Burp Suite's [Collaborator](https://portswigger.net/burp/documentation/collabora
is fetching content based on the `x5u` or `jku` headers.
Note that this functionality is only available in Burp Suite Professional.

### Weak HMAC secret
Attempt to brute-force the signing key for JWS with HMAC signatures using known [JWT secrets](https://github.com/wallarm/jwt-secrets).

## Issues / Enhancements
If you have found a bug or think that a particular feature is missing, please raise an issue on the [GitHub repository](https://github.com/DolphFlynn/jwt-editor/issues).

Expand Down

0 comments on commit 1fa506d

Please sign in to comment.