The NAAS 3.x before 3.10.0 API keys were generated using an insecure pseudo-random string and hashing algorithm which could lead to predictable keys.
Weakness
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Nginx_controller |
F5 |
3.0.0 (including) |
3.10.0 (excluding) |
Potential Mitigations
- 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.
References