IBM GSKit (IBM DB2 for Linux, UNIX and Windows 9.7, 10.1, 10.5, and 11.1) duplicates the PRNG state across fork() system calls when multiple ICC instances are loaded which could result in duplicate Session IDs and a risk of duplicate key material. IBM X-Force ID: 139071.
The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Db2 | Ibm | 9.7 (including) | 9.7 (including) |
| Db2 | Ibm | 10.1 (including) | 10.1 (including) |
| Db2 | Ibm | 10.5 (including) | 10.5 (including) |
| Db2 | Ibm | 11.1 (including) | 11.1 (including) |
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:
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.