| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Segmentio is-url up to 1.2.2. It has been declared as problematic. This vulnerability affects unknown code of the file index.js. Such manipulation leads to redos. This vulnerability is listed as CVE-2018-25079. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Segmentio is-url up to 1.2.2. It has been rated as problematic. Affected by this issue is some unknown processing of the file index.js. The manipulation with an unknown input leads to a redos vulnerability. Using CWE to declare the problem leads to CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. Impacted is availability.
The weakness was presented 02/02/2023 as 18. The advisory is available at github.com. This vulnerability is handled as CVE-2018-25079. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1449.003 by the MITRE ATT&CK project.
Upgrading to version 1.2.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 149550935c63a98c11f27f694a7c4a9479e53794 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. The advisory contains the following remark:
As disclosed by email, the regex in this module was vulnerable to catastrophic backtracking. This could be used as a REDOS vector for Node.js servers that use this module.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/segmentio/is-url/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: 🔍
Exploiting
Class: RedosCWE: CWE-1333 / CWE-400 / CWE-404
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: is-url 1.2.3
Patch: 149550935c63a98c11f27f694a7c4a9479e53794
Timeline
02/02/2023 🔍02/02/2023 🔍
02/02/2023 🔍
03/04/2023 🔍
Sources
Product: github.comAdvisory: 18
Status: Confirmed
CVE: CVE-2018-25079 (🔍)
GCVE (CVE): GCVE-0-2018-25079
GCVE (VulDB): GCVE-100-220058
Entry
Created: 02/02/2023 20:58Updated: 03/04/2023 09:07
Changes: 02/02/2023 20:58 (44), 03/04/2023 09:07 (2)
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.