Insecure Random Number Generator in stormpath/sdk

stormpath/sdk Updated 02 Oct 2025

Summary

29/05/2024
MODERATE
No i
Moderate
5.3

GHSA-q8fc-v85f-78pw: stormpath/sdk uses Insecure Random Number Generator. Affects stormpath/sdk versions < 1.19.0. No fix is published. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

stormpath/sdk is a PHP library available on Packagist that provides functionality for working with Stormpath, a user management and authentication service. It allows developers to integrate Stormpath into their PHP applications and provides various features for user authentication and authorization. However, the library is vulnerable to an insecure random number generator (RNG) issue.

Vulnerability Detail

The vulnerability in stormpath/sdk arises from the insecure generation of UUID version 4. The library uses an insecure random number generator, which can lead to predictable UUIDs being generated. UUIDs are supposed to be unique identifiers, and the use of an insecure RNG compromises their uniqueness and can have security implications. An attacker may be able to guess or predict UUIDs, which can lead to various attacks such as session fixation, privilege escalation, or information disclosure.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended solution is to update the library to a fixed version.

Conclusion

The stormpath/sdk library is vulnerable to an insecure random number generator issue, which can compromise the uniqueness of generated UUIDs and lead to security risks. To mitigate this vulnerability, it is recommended to update the library to a fixed version that uses a secure random number generator. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for stormpath/sdk →

Share this vulnerability

FAQ

stormpath/sdk is a PHP library that provides functionality for working with Stormpath, a user management and authentication service. It helps developers integrate Stormpath into their PHP applications.

An insecure random number generator is a function or algorithm that generates random numbers in a predictable or non-random manner. This can lead to security vulnerabilities, as attackers may be able to guess or predict the generated numbers.

A UUID (Universally Unique Identifier) is a 128-bit identifier that is supposed to be unique across all devices and time. It is commonly used for generating unique identifiers in various applications and systems.

The insecure random number generator in stormpath/sdk can lead to predictable UUIDs being generated. This can enable various attacks such as session fixation, privilege escalation, or information disclosure.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the composer.lock file.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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