websocket-extensions up to 0.1.4 on Ruby Regex Backslash incorrect regex
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in websocket-extensions up to 0.1.4 on Ruby. Impacted is an unknown function of the component Regex Handler. Performing a manipulation as part of Backslash results in incorrect regex. This vulnerability is known as CVE-2020-7663. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in websocket-extensions up to 0.1.4 on Ruby (Ruby Gem). It has been classified as problematic. This affects an unknown code of the component Regex Handler. The manipulation as part of a Backslash leads to a incorrect regex vulnerability. CWE is classifying the issue as CWE-185. The product specifies a regular expression in a way that causes data to be improperly matched or compared. This is going to have an impact on availability. The summary by CVE is:
websocket-extensions ruby module prior to 0.1.5 allows Denial of Service (DoS) via Regex Backtracking. The extension parser may take quadratic time when parsing a header containing an unclosed string parameter value whose content is a repeating two-byte sequence of a backslash and some other character. This could be abused by an attacker to conduct Regex Denial Of Service (ReDoS) on a single-threaded server by providing a malicious payload with the Sec-WebSocket-Extensions header.
The weakness was published 06/02/2020. This vulnerability is uniquely identified as CVE-2020-7663 since 01/21/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.1.5 eliminates this vulnerability.
Similar entry is available at VDB-155984. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Incorrect regexCWE: CWE-185 / CWE-697
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: websocket-extensions 0.1.5
Timeline
01/21/2020 🔍06/02/2020 🔍
06/03/2020 🔍
06/03/2020 🔍
Sources
Status: Not definedCVE: CVE-2020-7663 (🔍)
GCVE (CVE): GCVE-0-2020-7663
GCVE (VulDB): GCVE-100-155985
See also: 🔍
Entry
Created: 06/03/2020 08:24Updated: 06/03/2020 08:29
Changes: 06/03/2020 08:24 (39), 06/03/2020 08:29 (18)
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.