Is CVE-2017-16028 exploited in the wild?

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

How severe is CVE-2017-16028?

Low severity, with a CVSS score of 3, published 9 October 2018.

Which products and versions are affected?

randomatic (npm) SEMVER:introduced=0,fixed=3.0.0.

Is there a fix for CVE-2017-16028?

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

How is CVE-2017-16028 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2017-16028?

Check whether you run randomatic (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-16028: randomatic cryptographically weak PRNG

CVE-2017-16028 · Severity: low · CVSS 3 · Published 2018-10-09

randomatic is a Node.js library for generating random strings and patterns. The library uses a cryptographically weak random number generator, allowing an attacker to predict the values it generates instead of receiving truly random output. This could compromise applications that rely on randomatic for security-sensitive operations like token generation or cryptographic nonce creation.

Vendors: npm.

Quick answers

Is CVE-2017-16028 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-16028 being exploited in the wild.
How severe is CVE-2017-16028?: Low severity, with a CVSS score of 3, published 9 October 2018.
Which products and versions are affected?: randomatic (npm) SEMVER:introduced=0,fixed=3.0.0.
Is there a fix for CVE-2017-16028?: Yes. randomatic (npm): upgrade to 3.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-16028 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2017-16028?: Check whether you run randomatic (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

randomatic (npm): upgrade to 3.0.0 or later
```
npm install randomatic@3.0.0
```

Technical details

randomatic generates random values using Math.random() instead of a cryptographically secure random number generator, making the output predictable (CWE-330, CWE-338). The vulnerability affects all versions prior to 3.0.0, which introduced the use of the crypto module for secure randomness. An unauthenticated network attacker can predict random values generated by the library, compromising any security-dependent functionality relying on randomatic for randomness. Applications using the library for token generation, nonce creation, or other cryptographic purposes are particularly at risk.

Affected products

jonschlinkert randomatic 0 to 2.3.0

Identifiers

CVE-2017-16028
GHSA-6g33-f262-xjp4

Timeline

2018-10-09: disclosed
2018-10-09: patched: Version 3.0.0 released with cryptographically secure random generation

References

https://github.com/jonschlinkert/randomatic/commit/4a526959b3a246ae8e4a82f9c182180907227fe1

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