CryptGenRandom is a deprecated^[1] cryptographically secure pseudorandom number generator function that is included in Microsoft CryptoAPI. In Win32 programs, Microsoft recommends its use anywhere random number generation is needed. A 2007 paper from Hebrew University suggested security problems in the Windows 2000 implementation of CryptGenRandom (assuming the attacker has control of the machine). Microsoft later acknowledged that the same problems exist in Windows XP, but not in Vista. Microsoft released a fix for the bug with Windows XP Service Pack 3 in mid-2008.^[2]

The Win32 API includes comprehensive support for cryptography through the Microsoft CryptoAPI, a set of cryptographic primitives provided by Microsoft for use in Windows applications. Windows technologies such as TLS support (via the Schannel API) and code signing rely on these primitives, which in turn rely on a cryptographically secure pseudorandom number generator (CSPRNG). CryptGenRandom is the standard CSPRNG supplied with the Microsoft CryptoAPI.

Microsoft-provided cryptography providers share the same implementation of CryptGenRandom, currently based on an internal function called RtlGenRandom.^[3] Only a general outline of the algorithm had been published as of 2007^[update]:

[RtlGenRandom] generates as specified in FIPS 186-2 appendix 3.1 with SHA-1 as the G function. And with entropy from:

• The current process ID (GetCurrentProcessID).
• The current thread ID (GetCurrentThreadID).
• The tick count since boot time (GetTickCount).
• The current time (GetLocalTime).
• Various high-precision performance counters (QueryPerformanceCounter).
• An MD4 hash of the user's environment block, which includes username, computer name, and search path. [...]
• High-precision internal CPU counters, such as RDTSC, RDMSR, RDPMC

[omitted: long lists of low-level system information fields and performance counters] ^[4]

Microsoft has documented the implementation of the Windows 10 random number generator in some detail, in a whitepaper published in 2019.^[5] In Windows 10:

• There exists a hierarchy of random number generators. The kernel has a "Root" PRNG, from which all randomness is ultimately derived. The kernel then uses the Root PRNG to seed one PRNG per logical processor (so the PRNG state is thread-local and requires no locking). When a process launches, it requests random bytes from the kernel per-processor PRNG to seed its own Process PRNG. It then uses the Process PRNG to also seed one buffered PRNG per logical processor.^[5]
• All userspace calls to fetch randomness, be it CryptGenRandom or RtlGenRandom, ultimately fall to ProcessPrng, which returns bytes from the process's per-processor PRNG. The PRNG always uses the AES-CTR-DRBG algorithm as specified by FIPS SP800-90. Although BCryptGenRandom accepts requests for older algorithms for backward compatibility, it only ever return random numbers from the per-processor PRNG.^[5]: 8
  • AES-CTR-DRBG, instead of FIPS 186, has been the default since Windows Vista and Windows Server 2008.^[6]
  • The removal of other algorithms happened in Windows 10.^[6]
• The root RNG is periodically reseeded from the entropy pools.^[5]: 9 At bootup when very little entropy is available, a special "initial seeding" procedure provides the seed from seed files, external entropy, TPM randomness, RDRAND/RDSEED instructions, ACPI-OEM0 table, UEFI entropy, and the current time.^[5]: 11
• The kernel maintains multiple entropy pools. Multiple entropy sources append into pools, the main one being interrupt timing.^[5]: 12 When a pool is used, the SHA-512 hash of its contents is taken as the output.^[5]: 10 Windows does not estimate entropy.^[5]: 16

The security of a cryptosystem's CSPRNG is crucial because it is the origin for dynamic key material. Keys needed "on the fly", such as the TLS session keys that protect HTTPS connections, originate from CSPRNGs. If these pseudorandom numbers are predictable, session keys are predictable as well. Because CryptGenRandom is the de facto standard CSPRNG in Win32 environments, its security is critical for Windows users.

A cryptanalysis of CryptGenRandom, published in November 2007 by Leo Dorrendorf and others from the Hebrew University of Jerusalem and University of Haifa, found significant weaknesses in the Windows 2000 implementation of the algorithm.^[7]

To take advantage of the vulnerability, an attacker would first need to compromise the program running the random number generator. The weaknesses in the paper all depend on an attacker siphoning the state bits out of the generator. An attacker in a position to carry out this attack would typically already be in a position to defeat any random number generator (for instance, they can simply sniff the outputs of the generator, or fix them in memory to known values). However, the Hebrew University team notes that an attacker only need steal the state bits once in order to persistently violate the security of a CryptGenRandom instance. They can also use the information they glean to determine past random numbers that were generated, potentially compromising information, such as credit card numbers, already sent.

The paper's attacks are based on the fact that CryptGenRandom uses the stream cipher RC4, which can be run backwards once its state is known. They also take advantage of the fact that CryptGenRandom runs in user mode, allowing anyone who gains access to the operating system at user level, for example by exploiting a buffer overflow, to get CryptGenRandom's state information for that process. Finally, CryptGenRandom refreshes its seed from entropy infrequently. This problem is aggravated by the fact that each Win32 process has its own instance of CryptGenRandom state; while this means that a compromise of one process does not transitively compromise every other process, it may also increase the longevity of any successful break.

Because the details of the CryptGenRandom algorithm were not public at the time, Dorrendorf's team used reverse engineering tools to discern how the algorithm works. Their paper is the first published record of how the Windows cryptographic random number generator operates^{[citation needed]}.

Windows 2000, XP and 2003 have all successfully undergone EAL4+ evaluations, including the CryptGenRandom() and FIPSGenRandom() implementations. The Security Target documentation is available at the Common Criteria Portal, and indicates compliance with the EAL4 requirements. Few conclusions can be drawn about the security of the algorithm as a result; EAL4 measures products against best practices and stated security objectives, but rarely involves in-depth cryptanalysis.

This section may require cleanup to meet Wikipedia's quality standards. The specific problem is: Incomplete list; just going to the rngval page and Ctrl-F for "Microsoft Corp" is easier. Do we really want to complete the list? It's boring and repetitive, and all it does is show FIPS 186-2 conformance. Please help improve this section if you can. (March 2024) (Learn how and when to remove this message)

Microsoft has obtained validation of its RNG implementations in the following environments:

• Windows Vista and Server 2008 RNG Implementation (certificate 435)^[8]
• Windows Vista RNG implementations (certificate 321)^[8]
• Windows 2003 Enhanced Cryptographic Provider (rsaenh.dll) (certificate 316)^[8]
• Windows 2003 Enhanced DSS and Diffie-Hellman Cryptographic Provider (dssenh.dll) (certificate 314)^[8]
• Windows 2003 Kernel Mode Cryptographic Module (fips.sys) (certificate 313)^[8]
• Windows CE and Windows Mobile Enhanced Cryptographic Provider (rsaenh.dll) (certificate 292)^[8]
• Windows CE and Windows Mobile Enhanced Cryptographic Provider (rsaenh.dll) (certificate 286)^[8]
• Windows CE Enhanced Cryptographic Provider (rsaenh.dll) (certificate 66)^[8]

These tests are "designed to test conformance to the various approved RNG specifications rather than provide a measure of a product’s security. [...] Thus, validation should not be interpreted as an evaluation or endorsement of overall product security." Few conclusions can be drawn about the security of the algorithm as a result; FIPS evaluations do not necessarily inspect source code or evaluate the way RNG seeds are generated.^[9]

The RNG validation list carries the following notice: "As of January 1, 2016, in accordance with the SP800-131A Revision 1 Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths, the use of RNGs specified in FIPS 186-2, [X9.31], and the 1998 version of [X9.62] is no longer approved. This list is provided for historical purposes only."^[10]

Windows developers have several alternative means of accessing the CryptGenRandom functionality; these alternatives invoke the same algorithm and share the same security characteristics, but may have other advantages.

If backwards compatibility up to Windows XP is required for your program, the Windows API function RtlGenRandom (which resides in advapi32.dll^[3]) can be called to generate secure random data, as shown below. If this is not an issue, the program should use the newer BCryptGenRandom call instead.

Historically, we always told developers not to use functions such as rand to generate keys, nonces and passwords, rather they should use functions like CryptGenRandom, which creates cryptographically secure random numbers. The problem with CryptGenRandom is you need to pull in CryptoAPI (CryptAcquireContext and such) which is fine if you're using other crypto functions.

On a default Windows XP and later install, CryptGenRandom calls into a function named ADVAPI32!RtlGenRandom, which does not require you load all the CryptAPI stuff. In fact, the new Whidbey CRT function, rand_s calls RtlGenRandom.^[11]

Programmers using .NET should use the RNGCryptoServiceProvider Class.^[12]

The CNG ^[13] is a long term replacement for the deprecated Crypto API. It provides an equivalent function BCryptGenRandom^[14] as well as dedicated functions for key generation.

• the Microsoft C library function rand_s uses RtlGenRandom to generate cryptographically secure random numbers.^[11]
• the Python function urandom in the os module, which uses /dev/urandom on Unix-like systems, calls CryptGenRandom on Windows systems.^[15]
• the SunMSCAPI JCA provider available with OpenJDK and Oracle distributions of the JRE on Windows provides a SecureRandom implementation with the algorithm name Windows-PRNG. This class forwards all queries for random or seed bytes as well as setting additional seed bytes to CryptGenRandom.^[16]

• Entropy-supplying system calls – the approximate equivalent of CryptGenRandom in OpenBSD and the Linux kernel
• /dev/random – a randomness source in most Unix-like kernels
• Random number generator attack

• Microsoft Shared Source licensing programs