CVE-2020-15240
Summary
| CVE | CVE-2020-15240 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-10-21 18:15:00 UTC |
| Updated | 2021-11-18 16:21:00 UTC |
| Description | 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. |
Risk And Classification
Problem Types: CWE-347
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Auth0 | Omniauth-auth0 | All | All | All | All |
| Application | Auth0 | Omniauth-auth0 | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| omniauth-auth0 | RubyGems.org | your community gem host | MISC | rubygems.org | Product, Vendor Advisory |
| Verify the JWT signature · auth0/omniauth-auth0@fd3a14f · GitHub | MISC | github.com | Patch, Third Party Advisory |
| Regression in JWT Signature Validation · Advisory · auth0/omniauth-auth0 · GitHub | CONFIRM | github.com | Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.