CVE-2017-16028: Cryptographically Weak PRNG in randomatic

randomatic Updated 02 Oct 2025

Summary

09/10/2018
Yes i
Moderate
5.3

CVE-2017-16028: Cryptographically Weak PRNG in randomatic. Affects randomatic versions < 3.0.0. Fixed in 3.0.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The randomatic package is an npm package that generates random values. It is commonly used in applications that require random string generation, such as password generators or unique identifier creation. The package utilizes a pseudo-random number generator (PRNG) to generate these random values. However, certain versions of randomatic have been found to use a cryptographically weak PRNG, which can result in predictable values instead of truly random ones.

Vulnerability Detail

The vulnerability in randomatic arises from the use of a weak PRNG. This means that the generated random values are not truly random and can be predicted or guessed by an attacker. This can have serious security implications, especially in applications where random values are used for cryptographic purposes or to ensure uniqueness. An attacker who can predict the random values generated by randomatic may be able to bypass security measures or launch targeted attacks.

How To Fix

Minimum fixed version

3.0.0

This is the first release that contains the fix.

npm install randomatic@3.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The best course of action is to update to the latest version of the randomatic package.

Conclusion

The randomatic package has a vulnerability that stems from the use of a weak pseudo-random number generator. This can result in predictable random values, which can have serious security implications. To mitigate this vulnerability, it is crucial to update to version 3.0.0 or later of the package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for randomatic →

Share this vulnerability

FAQ

randomatic is an npm package used for generating random values, such as random strings or unique identifiers.

A pseudo-random number generator is an algorithm that generates a sequence of numbers that appear to be random but are actually determined by a starting value called a seed. In the case of randomatic, the weak PRNG used means that the generated values are not truly random and can be predicted.

The use of a weak PRNG in randomatic can have serious security implications. Attackers may be able to predict the random values generated by the package, which can lead to bypassing security measures or launching targeted attacks.

To fix this vulnerability, update to version 3.0.0 or later of the randomatic package.

There is no specific workaround mentioned for this vulnerability. It is recommended to update to the latest version of the randomatic package.

How To Fix

Minimum fixed version

3.0.0

This is the first release that contains the fix.

npm install randomatic@3.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback