Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2020-15240

HIGH
Published 2020-10-21T17:25:14
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2020-15240. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
7.4
/10
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.001
probability
of exploitation in the wild

There is a 0.1% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.261
Higher than 26.1% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED

Impact Metrics

Confidentiality
HIGH
Integrity
HIGH
Availability
NONE

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

auth0

omniauth-auth0

Affected Versions:

>= 2.3.0, <2.4.1

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed HIGH

Regression in JWT Signature Validation

GHSA-58r4-h6v8-jcvm

Advisory Details

### Overview Versions after and including `2.3.0` are improperly validating the JWT token signature when using the `JWTValidator.verify` method. 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.verify` method 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.

Affected Packages

RubyGems omniauth-auth0
ECOSYSTEM: ≥2.3.0 <2.4.1

CVSS Scoring

CVSS Score

7.5

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

References

WEB https://github.com/auth0/omniauth-auth0/security/advisories/GHSA-58r4-h6v8-jcvm
ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2020-15240
WEB https://github.com/auth0/omniauth-auth0/commit/fd3a14f4ccdfbc515d1121d6378ff88bf55a7a7a
PACKAGE https://github.com/auth0/omniauth-auth0
WEB https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth-auth0/CVE-2020-15240.yml
WEB https://rubygems.org/gems/omniauth-auth0

Advisory provided by GitHub Security Advisory Database. Published: November 3, 2020, Modified: May 16, 2023

References

https://github.com/auth0/omniauth-auth0/security/advisories/GHSA-58r4-h6v8-jcvm
https://github.com/auth0/omniauth-auth0/commit/fd3a14f4ccdfbc515d1121d6378ff88bf55a7a7a
https://rubygems.org/gems/omniauth-auth0
Published: 2020-10-21T17:25:14
Last Modified: 2024-08-04T13:08:22.896Z
Copied to clipboard!