Security weakness
CWE-335 Incorrect Usage of Seeds in Pseudo-Random Number Generator
A base-level weakness that can lead to accounts and admin areas exposed. Here is what it is, what it can cost you and how to close it.
- Senior security engineers
- 540+ projects delivered
- Reply within one business day
Quick answer
What is CWE-335?
Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG): The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.
Business impact
What CWE-335 could cost your business
MITRE documents what this weakness can do. Here is what that means for a website, store or app.
Access Control
Accounts and admin areas exposed
Logins and permission checks can be bypassed, putting admin and customer accounts at risk.
- Bypass Protection Mechanism
- Other
Free security check
Is CWE-335 hiding in your site?
A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.
Official definition
How MITRE defines CWE-335
Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)
The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.
PRNGs are deterministic and, while their output appears random, they cannot actually create entropy. They rely on cryptographically secure and unique seeds for entropy so proper seeding is critical to the secure operation of the PRNG.
Management of seeds could be broken down into two main areas:
(1) protecting seeds as cryptographic material (such as a cryptographic key);
(2) whenever possible, using a uniquely generated seed from a cryptographically secure source
PRNGs require a seed as input to generate a stream of numbers that are functionally indistinguishable from random numbers. While the output is, in many cases, sufficient for cryptographic uses, the output of any PRNG is directly determined by the seed provided as input. If the seed can be ascertained by a third party, the entire output of the PRNG can be made known to them. As such, the seed should be kept secret and should ideally not be able to be guessed. For example, the current time may be a poor seed. Knowing the approximate time the PRNG was seeded greatly reduces the possible key space.
Seeds do not necessarily need to be unique, but reusing seeds may open up attacks if the seed is discovered.
Detection and evidence
How CWE-335 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
How it is detected
- Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.
Real vulnerabilities it caused
- CVE-2020-7010Cloud application on Kubernetes generates passwords using a weak random number generator based on deployment time.
- CVE-2019-11495server uses erlang:now() to seed the PRNG, which results in a small search space for potential random seeds
- CVE-2018-12520Product’s PRNG is not seeded for the generation of session IDs
- CVE-2016-10180Router’s PIN generation is based on rand(time(0)) seeding.
How we fix it
From finding to fixed: how Codefreex closes CWE-335
- 01
Scan and confirm
We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.
- 02
Fix at the source
We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.
- 03
Verify the fix
We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.
- 04
Keep it fixed
Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.
Website SecurityPenetration TestingMalware Removal & Hack RepairWordPress Maintenance
Related weaknesses
Weaknesses related to CWE-335
FAQ
CWE-335: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
What is CWE-335?
CWE-335, “Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.
How serious is CWE-335?
It can affect access control, other, with impacts such as bypass protection mechanism, other. The real risk depends on where the weakness sits and what data or functions it exposes.
Can Codefreex check my site for CWE-335?
Yes. A senior engineer reviews your site, store or app for CWE-335 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.
Free security check
Find out if CWE-335 affects your site
Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.
- A senior strategist reviews your request, not a sales bot
- Clear scope, timeline and estimate within one business day
- Free 30-minute discovery call, no obligation
- NDA available on request
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.