A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. Same 2 factor Authentication secret code was generated which resulted an attacker to maintain access under certain conditions.
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 |
| Gitlab |
Gitlab |
* |
13.1.10 (excluding) |
| Gitlab |
Gitlab |
13.2.0 (including) |
13.2.8 (excluding) |
| Gitlab |
Gitlab |
13.3.0 (including) |
13.3.4 (excluding) |
| Gitlab |
Ubuntu |
esm-apps/xenial |
* |
| Gitlab |
Ubuntu |
upstream |
* |
| Gitlab |
Ubuntu |
xenial |
* |
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