Regression in JWT Signature Validation
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-287.
Summary
omniauth-auth0 (rubygems) versions >= 2.3.0 and < 2.4.1 improperly validate the JWT token signature when using the `jwt_validator.verify` method. Improper validation of the JWT token signature can allow an attacker to bypass authentication and authorization. You are affected by this vulnerability if all of the following conditions apply: 1. You are using `omniauth-auth0`. 2. You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow. The issue is patched in version 2.4.1.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| auth0 | omniauth-auth0 | 2.3.0 to before 2.4.1 | 2.4.1 | Patch available | CNA |
| — | omniauth-auth0 (RubyGems) | 2.3.0 to before 2.4.1 | 2.4.1 | Patch available | GHSA-58r4-h6v8-jcvm |
- omniauth-auth0 Vendorauth0 Affected 2.3.0 to before 2.4.1 Fixed in 2.4.1 Patch available CNA
- omniauth-auth0 (RubyGems) Vendor— Affected 2.3.0 to before 2.4.1 Fixed in 2.4.1 Patch available GHSA-58r4-h6v8-jcvm
Remediation
- Fix · CNA omniauth-auth0 (auth0) Fixed in 2.4.1
- Fix · GHSA-58r4-h6v8-jcvm omniauth-auth0 (RubyGems) Fixed in 2.4.1 Advisory →
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2020-15240
- 2026-10-03 Alias added: GHSA-58r4-h6v8-jcvm
References
Advisory 3
Sources
- CVE-2020-15240 · CVE Program
- CVE-2020-15240 · NVD
- FIRST EPSS
- GHSA-58r4-h6v8-jcvm · GitHub Advisory Database · CC BY 4.0
- CVE-2020-15240 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences