Omniauth Auth0
Approved changes feed: RSS · Atom
cpe:2.3:a:auth0:omniauth-auth0:*:*:*:*:*:ruby:*:*
part: a version: * update: *
| Vendor | Auth0 (bd827468-a826-51d4-9e05-912ec56b4756) |
|---|---|
| Product | Omniauth Auth0 (fdc70ec1-d4ab-5c6a-9770-c8ea42588b7f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | ruby |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-15240 |
vulnerable | 2026-06-03 14:41:45.549676 |
Regression in JWT Signature Validation
HIGH (7.4)
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.
Published: 2020-10-21T17:25:14.000Z
Updated: 2024-08-04T13:08:22.896Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.