CWE-330: Use of Insufficiently Random Values
ClassLikelihood of exploit: High
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
Consequences
- Confidentiality, Other: Other
- Access Control, Other: Bypass Protection Mechanism, Other
- Access Control: Bypass Protection Mechanism, Gain Privileges or Assume Identity
How to prevent it
- Architecture and Design: Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a "random enough" number.
- Implementation: Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
- Architecture and Design, Requirements: Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").
Recent advisories
- EEF-CVE-2026-81852 — AshAdmin ships a hardcoded CSP nonce, allowing nonce-based CSP bypass
- GHSA-qv2q-c278-pch5 — ImageMagick: Information Disclosure in PasskeyEncipherImage via AES-CTR nonce reuse
- GHSA-2rhw-gw3f-477j — DNN: Same HostGUID for all new installs
- GHSA-9jpj-g8vv-j5mf — OpenClaw: Gemini OAuth exposed the PKCE verifier through the OAuth state parameter
- GHSA-vfgx-5q85-58q3 — openssl-encrypt has non-cryptographic PRNG used for steganography pixel selection
- GHSA-pfjf-5gxr-995x — Gradio has an Open Redirect in its OAuth Flow
- GHSA-ppwx-5jq7-px2w — Fleet: Device lock PIN can be predicted if lock time is known
- GHSA-hv93-r4j3-q65f — OpenClaw Hook Session Key Override Enables Targeted Cross-Session Routing
- GHSA-c76h-2ccp-4975 — Use of Insufficiently Random Values in undici
- GHSA-mh98-763h-m9v4 — JUJU_CONTEXT_ID is a predictable authentication secret
- GHSA-8c69-r38j-rpfj — Rancher cattle-token is predictable
- GHSA-v9gv-xp36-jgj8 — RabbitMQ has predictable credential obfuscation seed value used in Shovel and Federation plugins
- GO-2022-0531 — Session tickets lack random ticket_age_add in crypto/tls
- GHSA-2m7h-86qq-fp4v — Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
- GHSA-qp4f-2w67-c8hw — Inbound TCP Agent Protocol/3 authentication bypass in Jenkins
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor