-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: auth0/node-jsonwebtoken
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.1.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: auth0/node-jsonwebtoken
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.2.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 5 files changed
- 1 contributor
Commits on Mar 16, 2015
-
Configuration menu - View commit details
-
Copy full SHA for 316fa4a - Browse repository at this point
Copy the full SHA 316fa4aView commit details -
Configuration menu - View commit details
-
Copy full SHA for f9f3c34 - Browse repository at this point
Copy the full SHA f9f3c34View commit details -
Verification with an asymmetric key of a token signed with a symmetri…
…c key There is a vulnerability in this module when the verification part is expecting a token digitally signed with an asymetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family). The issue is because this library has the very same signature to verify both type of tokens (parameter: `secretOrPublicKey`). This change adds a new parameter to the verify called `algorithms`. This can be used to specify a list of supported algorithms, but the default value depends on the secret used: if the secretOrPublicKey contains the string `BEGIN CERTIFICATE` the default is `[ 'RS256','RS384','RS512','ES256','ES384','ES512' ]` otherwise is `[ 'HS256','HS384','HS512' ]`.
Configuration menu - View commit details
-
Copy full SHA for 1bb584b - Browse repository at this point
Copy the full SHA 1bb584bView commit details -
Merge pull request #69 from auth0/fix_alg_vuln_on_verify
Verification with an asymmetric key of a token signed with a symmetric key
Configuration menu - View commit details
-
Copy full SHA for c2bf7b2 - Browse repository at this point
Copy the full SHA c2bf7b2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7863a84 - Browse repository at this point
Copy the full SHA 7863a84View commit details
There are no files selected for viewing