Is CVE-2017-16023 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-16023 being exploited in the wild.

How severe is CVE-2017-16023?

Low severity, with a CVSS score of 3, published 24 July 2018.

Which products and versions are affected?

decamelize (npm) SEMVER:introduced=1.1.0,fixed=1.1.2.

Is there a fix for CVE-2017-16023?

Yes. decamelize (npm): upgrade to 1.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2017-16023 attacked?

It is attacked over the network.

Am I affected by CVE-2017-16023?

Check whether you run decamelize (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2017-16023: decamelize regular expression denial of service

CVE-2017-16023 · Severity: low · CVSS 3 · Published 2018-07-24

decamelize is a JavaScript library that converts camelCase strings into kebab-case format. The library is vulnerable to regular expression denial of service (ReDoS) attacks when processing untrusted input, allowing an attacker to cause the application to hang or consume excessive CPU resources by supplying specially crafted strings.

Vendors: npm.

Quick answers

Is CVE-2017-16023 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-16023 being exploited in the wild.
How severe is CVE-2017-16023?: Low severity, with a CVSS score of 3, published 24 July 2018.
Which products and versions are affected?: decamelize (npm) SEMVER:introduced=1.1.0,fixed=1.1.2.
Is there a fix for CVE-2017-16023?: Yes. decamelize (npm): upgrade to 1.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-16023 attacked?: It is attacked over the network.
Am I affected by CVE-2017-16023?: Check whether you run decamelize (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

decamelize (npm): upgrade to 1.1.2 or later
```
npm install decamelize@1.1.2
```

Technical details

The vulnerability is a regular expression denial of service (ReDoS, CWE-400) caused by an unvalidated separator parameter being passed directly into a regex pattern without proper escaping. When a user supplies a special regex metacharacter (such as the pipe "|") as the separator argument, it creates a malicious regular expression that exhibits catastrophic backtracking. An attacker can trigger this via network if the affected library processes user input without sanitization. The vulnerability affects versions 1.1.0 through 1.1.1; patched in version 1.1.2 and later.

Affected products

sindresorhus decamelize 1.1.0 through 1.1.1

Identifiers

CVE-2017-16023
GHSA-q5c4-39f5-m68j

Timeline

2015-12-23: disclosed: Issue reported on GitHub
2018-07-24: advisory: GHSA advisory published
2017: patched: Fixed in version 1.1.2

References

https://github.com/sindresorhus/decamelize/issues/5

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.