Generation of Predictable Numbers or Identifiers
CWE-340
The product uses a scheme that generates numbers or identifiers that are more predictable than required.
We track 30 vulnerabilities of this type. 97% are rated high or critical, and the average CVSS score is 8.4. 1 has been exploited in real attacks.
Latest Generation of Predictable Numbers or Identifiers vulnerabilities
- 9.1 Critical severity
VOS: Generation of Predictable Numbers or Identifiers
The Node.js web service on VOS (previously Versa FlexVNF) is used for URL-based Zero Touch Provisioning (ZTP) of the VOS appliance and is not required after provisioning is complete. This service generates session identifiers using UUID version 1 (UUIDv1), whi
- 4.3 Medium severity
Ivanti Connect Secure Generation of Predictable Numbers or Identifiers Exploited
Use of predictable filenames in Ivanti Connect Secure before versions 25.1.1.3 and 22.8R2.6 allows a remote authenticated attacker to upload files with attacker-controlled content to a known location on disk.
- 7.7 High severity
Cloud Run MCP: Generation of Predictable Numbers or Identifiers
Bucket Squatting in Google Cloud Run MCP versions prior to 1.11.0 on Google Cloud Platform allows an attacker to intercept and access proprietary source code, execute arbitrary code and exfiltrate data. Users must upgrade to Cloud Run MCP version 1.11.0 or lat
- 8.8 High severity
G980H: Generation of Predictable Numbers or Identifiers
The Botslab G980H dash camera firmware generates session identifiers using a small sequential value space rather than a suitably unpredictable source. An unauthenticated attacker with adjacent network access and knowledge that an active session exists could po
- 7.5 High severity
community_store: Generation of Predictable Numbers or Identifiers
Concrete CMS Community Store before 2.7.8 derives digital product download tokens from order creation timestamps instead of random values, making tokens predictable. Unauthenticated attackers can enumerate sequential order and file identifiers to calculate val
- 9.1 Critical severity
OpnForm: Generation of Predictable Numbers or Identifiers
OpnForm derives editable-submission secrets from sequential row identifiers using Hashids with an empty default salt, allowing unauthenticated attackers to compute hashes for any submission. Attackers can read other respondents' full submission data through th
- 9.0 Critical severity
manageengine_adselfservice_plus: Improper Authentication
In ManageEngine ADSelfService Plus, RecoveryManager Plus, M365 Manager Plus, and ADAudit Plus, the SSO tickets generated to authenticate that session could be predicted by an unauthenticated user, leading to account takeover.
- 9.1 Critical severity
Mojolicious::Plugin::Web::Auth::OAuth2: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Mojolicious::Plugin::Web::Auth::OAuth2 versions through 0.17 for Perl have an insecure default state parameter. When no state generator is specified in the constructor, the module defaults to using a SHA-1 hash of predictable and low-entropy sources, including
- 8.2 High severity
Apache::Session::Generate::ModUniqueId: Generation of Predictable Numbers or Identifiers
Apache::Session::Generate::ModUniqueId versions from 1.54 through 1.94 for Perl session ids are insecure. Apache::Session::Generate::ModUniqueId (added in version 1.54) uses the value of the UNIQUE_ID environment variable for the session id. The UNIQUE_ID vari
- 9.1 Critical severity
freescout: Use of Insufficiently Random Values
FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.213, attachment download tokens are generated using a weak and predictable formula: `md5(APP_KEY + attachment_id + size)`. Since attachment_id is sequential and size can be brut
- 9.1 Critical severity
Solstice::Session: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Solstice::Session versions through 1440 for Perl generates session ids insecurely. The _generateSessionID method returns an MD5 digest seeded by the epoch time, a random hash reference, a call to the built-in rand() function and the process id. The same method
- 9.8 Critical severity
HTTP::Session: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
HTTP::Session versions before 0.54 for Perl defaults to using insecurely generated session ids. HTTP::Session defaults to using HTTP::Session::ID::SHA1 to generate session ids using a SHA-1 hash seeded with the built-in rand function, the high resolution epoch
- 9.8 Critical severity
Amon2: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions. In versions 6.06 through 6.16, the random_string function will attempt to read bytes from the /dev/urandom device, but if that is unavailable then it gener
- 7.5 High severity
Bedrock AgentCore Starter Toolkit: Unverified Ownership
A missing S3 ownership verification in the Bedrock AgentCore Starter Toolkit before version v0.1.13 may allow a remote actor to inject code during the build process, leading to code execution in the AgentCore Runtime. This issue only affects users of the Bedro
- 9.1 Critical severity
Apache::Session::Generate::MD5: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Apache::Session::Generate::MD5 versions through 1.94 for Perl create insecure session id. Apache::Session::Generate::MD5 generates session ids insecurely. The default session id generator returns a MD5 hash seeded with the built-in rand() function, the epoch t
- 9.8 Critical severity
Plack::Middleware::Session::Simple: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Plack::Middleware::Session::Simple versions before 0.05 for Perl generates session ids insecurely. The default session id generator returns a SHA-1 hash seeded with the built-in rand function, the epoch time, and the PID. The PID will come from a small set of
- 8.2 High severity
Apache::SessionX: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Apache::SessionX versions through 2.01 for Perl create insecure session id. Apache::SessionX generates session ids insecurely. The default session id generator in Apache::SessionX::Generate::MD5 returns a MD5 hash seeded with the built-in rand() function, the
- 7.7 High severity
Vertex AI Experiments: Generation of Predictable Numbers or Identifiers
Predictable bucket naming in Vertex AI Experiments in Google Cloud Vertex AI from version 1.21.0 up to (but not including) 1.133.0 on Google Cloud Platform allows an unauthenticated remote attacker to achieve cross-tenant remote code execution, model theft, an
- 9.8 Critical severity
Concierge::Sessions: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Concierge::Sessions versions from 0.8.1 before 0.8.5 for Perl generate insecure session ids. The generate_session_id function in Concierge::Sessions::Base defaults to using the uuidgen command to generate a UUID, with a fallback to using Perl's built-in rand f
- 7.5 High severity
jervis: Use of a Broken or Risky Cryptographic Algorithm
Jervis is a library for Job DSL plugin scripts and shared Jenkins pipeline libraries. Prior to 2.2, Jervis uses deterministic AES IV derivation from a passphrase. This vulnerability is fixed in 2.2.
- 9.8 Critical severity
ragflow: Generation of Predictable Numbers or Identifiers
RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine. In versions prior to 0.22.0, the use of an insecure key generation algorithm in the API key and beta (assistant/agent share auth) token generation process allows these tokens to be mutually
- 7.5 High severity
SOPlanning: Generation of Predictable Numbers or Identifiers
SOPlanning is vulnerable to Predictable Generation of Password Recovery Token. Due to weak mechanism of generating recovery tokens, a malicious attacker is able to brute-force all possible values and takeover any account in reasonable amount of time. This issu
- 9.1 Critical severity
Starch: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Starch versions 0.14 and earlier generate session ids insecurely. The default session id generator returns a SHA-1 hash seeded with a counter, the epoch time, the built-in rand function, the PID, and internal Perl reference addresses. The PID will come from a
- 7.5 High severity
Apache::AuthAny: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Apache::AuthAny::Cookie v0.201 or earlier for Perl generates session ids insecurely. Session ids are generated using an MD5 hash of the epoch time and a call to the built-in rand function. The epoch time may be guessed, if it is not leaked from the HTTP Date h
- 8.6 High severity
Catalyst::Authentication::Credential::HTTP: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Catalyst::Authentication::Credential::HTTP versions 1.018 and earlier for Perl generate nonces using the Perl Data::UUID library. * Data::UUID does not use a strong cryptographic source for generating UUIDs. * Data::UUID returns v3 UUIDs, which are generated f
- 7.3 High severity
Plack::Middleware::Session: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Plack-Middleware-Session before version 0.35 for Perl generates session ids insecurely. The default session id generator returns a SHA-1 hash seeded with the built-in rand function, the epoch time, and the PID. The PID will come from a small set of numbers, an
- 7.1 High severity
pgAgent: Use of Insufficiently Random Values
When batch jobs are executed by pgAgent, a script is created in a temporary directory and then executed. In versions of pgAgent prior to 4.2.3, an insufficiently seeded random number generator is used when generating the directory name, leading to the possibil
- 7.5 High severity
macro-pdfviewer: Generation of Predictable Numbers or Identifiers
macro-pdfviewer is a PDF Viewer Macro for XWiki using Mozilla pdf.js. Any user with view right on XWiki.PDFViewerService can access any attachment stored in the wiki as the "key" that is passed to prevent this is computed incorrectly, calling skip on the diges
- 9.8 Critical severity
IoT Interface & CMC III Processing Unit: Insufficient Entropy
The devices are vulnerable to session hijacking due to insufficient entropy in its session ID generation algorithm. The session IDs are predictable, with only 32,768 possible values per user, which allows attackers to pre-generate valid session IDs, leading to
- 8.0 High severity
Juju: Use of Insufficiently Random Values
JUJU_CONTEXT_ID is a predictable authentication secret. On a Juju machine (non-Kubernetes) or Juju charm container (on Kubernetes), an unprivileged user in the same network namespace can connect to an abstract domain socket and guess the JUJU_CONTEXT_ID value.