Rack Module up to 2.2.2/2.1.3 on Ruby on Rails Cookie reliance on cookies without validation and integrity checking in a security decision
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Rack Module up to 2.2.2/2.1.3 on Ruby on Rails. This affects an unknown part of the component Cookie Handler. The manipulation leads to reliance on cookies without validation and integrity checking in a security decision. This vulnerability is traded as CVE-2020-8184. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Rack Module up to 2.2.2/2.1.3 on Ruby on Rails. It has been rated as critical. This issue affects an unknown code of the component Cookie Handler. The manipulation with an unknown input leads to a reliance on cookies without validation and integrity checking in a security decision vulnerability. Using CWE to declare the problem leads to CWE-784. The product uses a protection mechanism that relies on the existence or values of a cookie, but it does not properly ensure that the cookie is valid for the associated user. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possible for an attacker to forge a secure or host-only cookie prefix.
The weakness was shared 06/19/2020 (Website). The advisory is shared at groups.google.com. The identification of this vulnerability is CVE-2020-8184 since 01/28/2020. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.2.3 or 2.1.4 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Reliance on cookies without validation and integrity checking in a security decisionCWE: CWE-784
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: Rack Module 2.2.3/2.1.4
Timeline
01/28/2020 🔍06/19/2020 🔍
06/20/2020 🔍
06/20/2020 🔍
Sources
Advisory: groups.google.comStatus: Not defined
CVE: CVE-2020-8184 (🔍)
GCVE (CVE): GCVE-0-2020-8184
GCVE (VulDB): GCVE-100-157049
Entry
Created: 06/20/2020 08:18Updated: 06/20/2020 08:23
Changes: 06/20/2020 08:18 (39), 06/20/2020 08:23 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.