Vulnerabilities · 2020 · Auth0
CVE-2020-15240
Auth0 Omniauth-auth0 vulnerability
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.
Affected products
Omniauth-auth0. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Auth0 Omniauth-auth0 runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- rubygems.org/gems/omniauth-auth0 · Vendor Advisory
- github.com/auth0/omniauth-auth0/commit/fd3a14f4ccdfbc515d1121d6378ff88bf55a7a7a · Patch
- github.com/auth0/omniauth-auth0/security/advisories/GHSA-58r4-h6v8-jcvm · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-15240
- cve.org/CVERecord?id=CVE-2020-15240
More vulnerabilities in Auth0 products
CVE-2022-29172CVE-2022-24794CVE-2022-23541CVE-2022-23540CVE-2022-23539CVE-2022-23505CVE-2021-43812CVE-2021-41246All 34
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.