Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The random number generator is not compliant with Federal Processing Standard 140-2 in Windows Vista Service Pack 1 and in Windows Server 2008


View products that this article applies to.

Symptoms

In Windows Vista Service Pack 1 (SP1) and in Windows Server 2008, the random number generator (RNG) is not compliant with Federal Information Processing Standard (FIPS) 140-2.

This problem affects all the functions that use the RNG. The CryptoAPI function CryptGenRandom and the CNG function BCryptGenRandom use the RNG directly. Other functions that generate random numbers for keying material or for other purposes may also use the RNG indirectly.

Important This problem does not affect the external behavior of any functions that use the RNG. It does not affect the strength of any system cryptographic implementations. Additionally, it does not change cryptographic functionality in any other way.

↑ Back to the top


Cause

This problem occurs because certain internal self-tests are missing from the RNG.

↑ Back to the top


Resolution

A hotfix is available to resolve this problem. This hotfix contains changes to the cryptographic libraries in Windows Vista SP1 and in Windows Server 2008. These changes make the RNG fully compliant with the requirements of FIPS 140-2.

Note This hotfix does not change the functionality of the RNG.

After you install this hotfix, all cryptographic binaries that are affected will be updated with versions that contain the required self-tests.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

The following list contains prerequisites for the hotfix:
  • Windows Vista SP 1 or Windows Server 2008

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following hotfix:
953535 When many SSL connections are established on a Windows Server 2008-based computer, the computer eventually stops responding because of a memory leak

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Vista SP1 and Windows Server 2008, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,11113-Jun-200817:14Not Applicable
Package_2_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,27813-Jun-200817:14Not Applicable
Package_3_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,11813-Jun-200817:14Not Applicable
Package_4_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,11913-Jun-200817:14Not Applicable
Package_for_kb954059_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36713-Jun-200817:14Not Applicable
Package_for_kb954059_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43113-Jun-200817:14Not Applicable
Package_for_kb954059_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42213-Jun-200817:14Not Applicable
Package_for_kb954059_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42313-Jun-200817:14Not Applicable
Package_for_kb954059_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42613-Jun-200817:14Not Applicable
Package_for_kb954059_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43113-Jun-200817:14Not Applicable
Package_for_kb954059_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42213-Jun-200817:14Not Applicable
Package_for_kb954059_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43013-Jun-200817:14Not Applicable
Update.mumNot Applicable3,07713-Jun-200817:14Not Applicable
X86_29bb96108f142530a4b4139904adbb11_31bf3856ad364e35_6.0.6001.22202_none_76f028724b0cc0bc.manifestNot Applicable69813-Jun-200817:14Not Applicable
X86_37886f5f471fe55abb2f04da46cc338e_31bf3856ad364e35_6.0.6001.22202_none_47432becc2a223bb.manifestNot Applicable69813-Jun-200817:14Not Applicable
X86_3c26f70068358c36aa15c4a03aa99aeb_31bf3856ad364e35_6.0.6001.22202_none_319963a0c8e80f34.manifestNot Applicable69113-Jun-200817:14Not Applicable
X86_microsoft-windows-bcrypt-dll_31bf3856ad364e35_6.0.6001.22202_none_ef1832b20881782e.manifestNot Applicable3,70013-Jun-200804:55Not Applicable
X86_microsoft-windows-lsa_31bf3856ad364e35_6.0.6001.22202_none_a6d62a0775e707d5.manifestNot Applicable34,37313-Jun-200804:49Not Applicable
X86_microsoft-windows-rsaenh-dll_31bf3856ad364e35_6.0.6001.22202_none_6052af0cca604873.manifestNot Applicable5,70413-Jun-200804:49Not Applicable
Bcrypt.dll6.0.6001.22202274,43213-Jun-200803:20x86
Ksecdd.sys6.0.6001.22202441,40013-Jun-200803:57x86
Lsasrv.dll6.0.6001.222021,255,42413-Jun-200803:25x86
Lsasrv.mofNot Applicable13,78018-Dec-200721:23Not Applicable
Lsass.exe6.0.6001.222029,72813-Jun-200801:04x86
Secur32.dll6.0.6001.2220272,70413-Jun-200803:25x86
Rsaenh.dll6.0.6001.22202243,25613-Jun-200804:37x86
Windows Vista SP1 and Windows Server 2008, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,11113-Jun-200817:14Not Applicable
Package_2_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,27813-Jun-200817:14Not Applicable
Package_3_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,11813-Jun-200817:14Not Applicable
Package_4_for_kb954059~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable3,11913-Jun-200817:14Not Applicable
Package_for_kb954059_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36713-Jun-200817:14Not Applicable
Package_for_kb954059_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43113-Jun-200817:14Not Applicable
Package_for_kb954059_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42213-Jun-200817:14Not Applicable
Package_for_kb954059_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42313-Jun-200817:14Not Applicable
Package_for_kb954059_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42613-Jun-200817:14Not Applicable
Package_for_kb954059_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43113-Jun-200817:14Not Applicable
Package_for_kb954059_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42213-Jun-200817:14Not Applicable
Package_for_kb954059_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43013-Jun-200817:14Not Applicable
Update.mumNot Applicable3,07713-Jun-200817:14Not Applicable
X86_29bb96108f142530a4b4139904adbb11_31bf3856ad364e35_6.0.6001.22202_none_76f028724b0cc0bc.manifestNot Applicable69813-Jun-200817:14Not Applicable
X86_37886f5f471fe55abb2f04da46cc338e_31bf3856ad364e35_6.0.6001.22202_none_47432becc2a223bb.manifestNot Applicable69813-Jun-200817:14Not Applicable
X86_3c26f70068358c36aa15c4a03aa99aeb_31bf3856ad364e35_6.0.6001.22202_none_319963a0c8e80f34.manifestNot Applicable69113-Jun-200817:14Not Applicable
X86_microsoft-windows-bcrypt-dll_31bf3856ad364e35_6.0.6001.22202_none_ef1832b20881782e.manifestNot Applicable3,70013-Jun-200804:55Not Applicable
X86_microsoft-windows-lsa_31bf3856ad364e35_6.0.6001.22202_none_a6d62a0775e707d5.manifestNot Applicable34,37313-Jun-200804:49Not Applicable
X86_microsoft-windows-rsaenh-dll_31bf3856ad364e35_6.0.6001.22202_none_6052af0cca604873.manifestNot Applicable5,70413-Jun-200804:49Not Applicable
Bcrypt.dll6.0.6001.22202274,43213-Jun-200803:20x86
Ksecdd.sys6.0.6001.22202441,40013-Jun-200803:57x86
Lsasrv.dll6.0.6001.222021,255,42413-Jun-200803:25x86
Lsasrv.mofNot Applicable13,78018-Dec-200721:23Not Applicable
Lsass.exe6.0.6001.222029,72813-Jun-200801:04x86
Secur32.dll6.0.6001.2220272,70413-Jun-200803:25x86
Rsaenh.dll6.0.6001.22202243,25613-Jun-200804:37x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about FIPS 140 evaluation, visit the following Microsoft Web site:For more information about the BCryptGenRandom function, visit the following Microsoft Web site:For more information about the CryptGenRandom function, visit the following Microsoft Web site:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbqfe, KB954059

↑ Back to the top

Article Info
Article ID : 954059
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 414