TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 contains insecure randomness in the uniqid function.
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 |
| Typo3 |
Typo3 |
* |
4.1.14 (excluding) |
| Typo3 |
Typo3 |
4.2.0 (including) |
4.2.13 (excluding) |
| Typo3 |
Typo3 |
4.3.0 (including) |
4.3.4 (excluding) |
| Typo3 |
Typo3 |
4.4.0 (including) |
4.4.1 (excluding) |
| Typo3-src |
Ubuntu |
hardy |
* |
| Typo3-src |
Ubuntu |
lucid |
* |
| Typo3-src |
Ubuntu |
maverick |
* |
| Typo3-src |
Ubuntu |
upstream |
* |
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