CVE-2017-20165

HIGHCVSS 7.5/10EPSS 2.03%

Last modified

CVE-2017-20165 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. EPSS estimates a 2.03% chance of exploitation in the next 30 days.

Description

A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Upgrading to version 3.1.0 is able to address this issue. The identifier of the patch is c38a0166c266a679c8de012d4eaccec3f944e685. It is recommended to upgrade the affected component. The identifier VDB-217665 was assigned to this vulnerability.

Metrics

CVSS 3.1
7.5/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS Probability
2.03%

78.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Debug ProjectDebug< 2.6.9
Debug ProjectDebug>= 3.0.0, < 3.1.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-20165?
A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Upgrading to version 3.1.0 is able to address this issue. The identifier of the patch is c38a0166c266a679c8de012d4eaccec3f944e685. It is recommended to upgrade the affected component. The identifier VDB-217665 was assigned to this vulnerability.
How severe is CVE-2017-20165?
CVE-2017-20165 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 2.03% probability of exploitation in the next 30 days.
How do I fix CVE-2017-20165?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-20165?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST