GHSA-58r4-h6v8-jcvm
Suggest an improvement- Source
- https://github.com/advisories/GHSA-58r4-h6v8-jcvm
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/11/GHSA-58r4-h6v8-jcvm/GHSA-58r4-h6v8-jcvm.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-58r4-h6v8-jcvm
- Aliases
- Published
- 2020-11-03T02:31:38Z
- Modified
- 2023-11-08T04:02:34.983488Z
- Severity
-
- 7.4 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CVSS Calculator
- Summary
- Regression in JWT Signature Validation
- Details
-
Overview
Versions after and including
2.3.0are improperly validating the JWT token signature when using theJWTValidator.verifymethod. Improper validation of the JWT token signature when not using the default Authorization Code Flow can allow an attacker to bypass authentication and authorization.Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using
omniauth-auth0. - You are using
JWTValidator.verifymethod directly OR you are not authenticating using the SDK’s default Authorization Code Flow.
How to fix that?
Upgrade to version
2.4.1.Will this update impact my users?
The fix provided in this version will not affect your users.
- You are using
- Database specific
{ "nvd_published_at": "2020-10-21T18:15:00Z", "cwe_ids": [ "CWE-287", "CWE-347" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2020-10-27T19:10:29Z" }- References
-
- https://github.com/auth0/omniauth-auth0/security/advisories/GHSA-58r4-h6v8-jcvm
- https://nvd.nist.gov/vuln/detail/CVE-2020-15240
- https://github.com/auth0/omniauth-auth0/commit/fd3a14f4ccdfbc515d1121d6378ff88bf55a7a7a
- https://github.com/auth0/omniauth-auth0
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth-auth0/CVE-2020-15240.yml
- https://rubygems.org/gems/omniauth-auth0
Affected packages
RubyGems / omniauth-auth0
Package
- Name
- omniauth-auth0
- Purl
- pkg:gem/omniauth-auth0