omniauth-auth0 Gem 2.3.x/2.4.0 on Ruby JWT Token Signature Validation jwt_validator.verify improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in omniauth-auth0 Gem 2.3.x/2.4.0 on Ruby. Impacted is the function jwt_validator.verify of the component JWT Token Signature Validation. The manipulation results in improper authentication.
This vulnerability is known as CVE-2020-15240. It is possible to launch the attack remotely. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability was found in omniauth-auth0 Gem 2.3.x/2.4.0 on Ruby (Ruby Gem). It has been classified as critical. Affected is the function jwt_validator.verify of the component JWT Token Signature Validation. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 10/23/2020. The advisory is available at github.com. This vulnerability is traded as CVE-2020-15240. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
Upgrading to version 2.4.1 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: omniauth-auth0 Gem 2.4.1
Patch: github.com
Timeline
06/25/2020 🔍10/23/2020 🔍
10/23/2020 🔍
11/25/2020 🔍
Sources
Advisory: github.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-15240 (🔍)
GCVE (CVE): GCVE-0-2020-15240
GCVE (VulDB): GCVE-100-163410
Entry
Created: 10/23/2020 07:40Updated: 11/25/2020 19:07
Changes: 10/23/2020 07:40 (40), 11/25/2020 19:04 (3), 11/25/2020 19:07 (19)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.