CVE-2015-9235: Input Validation
First published: Tue May 29 2018(Updated: )
In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Auth0 Jsonwebtoken | <4.2.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2015-9235?
CVE-2015-9235 is considered to have a high severity due to the potential for attackers to bypass token verification.
How do I fix CVE-2015-9235?
To fix CVE-2015-9235, update the jsonwebtoken module to version 4.2.2 or later.
Which versions of jsonwebtoken are affected by CVE-2015-9235?
CVE-2015-9235 affects all versions of the jsonwebtoken module prior to 4.2.2.
What types of tokens are vulnerable in CVE-2015-9235?
CVE-2015-9235 allows attackers to exploit tokens signed with symmetric algorithms instead of asymmetric ones.
What is the impact of CVE-2015-9235 on applications using jsonwebtoken?
Applications using jsonwebtoken prior to version 4.2.2 may face unauthorized access due to flawed token verification.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- agent/severity
- agent/weakness
- agent/remedy
- agent/author
- agent/tags
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- vendor/auth0
- canonical/auth0 jsonwebtoken