cve.bz

CVE-2015-9235 auth0 jsonwebtoken: Improper Input Validation

9.8 criticalExploit referenceEPSS 8.4%Fix available

Critical (9.8) in auth0 jsonwebtoken. EPSS 8.4% estimated probability of exploitation activity in the next 30 days. Fixed in jsonwebtoken 4.2.2.

On this page
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).

Severity

CVSS 3.0

9.8 critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
8.4% (unchanged from 8.4% a week ago; 8.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 95th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
CWE-20 Improper Input Validation
OWASP Top 10
A04:2025 Cryptographic Failures, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2015-9235 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2015-9235?via=ask-ai-copy and https://cve.bz/cve/CVE-2015-9235?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2015-9235 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
auth0:jsonwebtokenbefore 4.2.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c7hr-j4mj-j2w6npmjsonwebtoken<4.2.24.2.2

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat Mobile Application Platform 4nodejs-jsonwebtokenNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2015-9235.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • tierChampion/POC_CVE-2015-9235 Harbor Check: matches CVE 0 stars, JavaScript, created
    Demo of the algorithm confusion attack on various JWT libraries

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON