CVE-2017-16099

Description

The no-case module is vulnerable to regular expression denial of service. When malicious untrusted user input is passed into no-case it can block the event loop causing a denial of service condition.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.33%
Third-Party Advisory github.com Third-Party Advisory nodesecurity.io
Affected: HackerOne no-case node module
Published at:
Updated at:

References

Link Tags
https://github.com/blakeembrey/no-case/issues/17 third party advisory
https://nodesecurity.io/advisories/529 third party advisory

Frequently Asked Questions

What is the severity of CVE-2017-16099?
CVE-2017-16099 has been scored as a high severity vulnerability.
How to fix CVE-2017-16099?
To fix CVE-2017-16099, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-16099 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-16099 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-16099?
CVE-2017-16099 affects HackerOne no-case node module.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.