Shrine up to 3.2.x derivation_endpoint Plugin Utils.secure_compare information exposure
| CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system. | Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack. | CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability. |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
A vulnerability, which was classified as problematic, was found in Shrine up to 3.2.x. This affects the function Rack::Utils.secure_compare of the component derivation_endpoint Plugin. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-203. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Shrine before version 3.3.0, when using the `derivation_endpoint` plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL. The problem has been fixed by comparing sent and calculated signature in constant time, using `Rack::Utils.secure_compare`. Users using the `derivation_endpoint` plugin are urged to upgrade to Shrine 3.3.0 or greater. A possible workaround is provided in the linked advisory.
The weakness was released 10/04/2020. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2020-15237 since 06/25/2020. The attack needs to be done within the local network. A authentication is necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 3.3.0 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.
Product
Name
CPE 2.3
CPE 2.2
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Information disclosureCWE: CWE-203
ATT&CK: Unknown
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | unlock | unlock | unlock | unlock |
|---|---|---|---|---|
| Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Threat: 🔍Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Shrine 3.3.0
Patch: github.com
Timeline
06/25/2020 CVE assigned10/04/2020 Advisory disclosed
10/06/2020 VulDB entry created
11/16/2020 VulDB last update
Sources
Advisory: github.comStatus: Confirmed
Confirmation: 🔒
CVE: CVE-2020-15237 (🔒)
Entry
Created: 10/06/2020 10:27 AMUpdated: 11/16/2020 05:02 PM
Changes: (7) vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai source_cve_cna
Complete: 🔍
Comments
Do you need the next level of professionalism?
Upgrade your account now!
No comments yet. Please log in to comment.