Microsoft Security Bulletin MS07-032 - Moderate
Vulnerability in Windows Vista Could Allow Information Disclosure (931213)
Published: June 12, 2007
This moderate security update resolves a privately reported vulnerability. This vulnerability could allow non-privileged users to access local user information data stores including administrative passwords contained within the registry and local file system.
This is a moderate security update for all supported editions of Windows Vista. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update addresses the vulnerability by setting Access Control Lists on user information stores that restrict access to privileged users. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation: Microsoft recommends that customers consider applying the security update.
Known Issues: None.
Affected and Non-Affected Software
The software listed here has been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
|Operating System||Maximum Security Impact||Aggregate Severity Rating||Bulletins Replaced by This Update|
|Windows Vista||Information Disclosure||Moderate||None|
|Windows Vista x64 Edition||Information Disclosure||Moderate||None|
|Windows 2000 Service Pack 4|
|Windows XP Service Pack 2|
|Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2|
|Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2|
|Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2|
|Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems|
Frequently Asked Questions (FAQ) Related to This Security Update
I am using an older version or edition of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin has been tested to determine which versions or editions are affected. Other versions and editions are past their support life cycle. To determine the support life cycle for your product and version, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older versions or editions of the software to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Severity Ratings and Vulnerability Identifiers
|Affected Software||Permissive User Information Store ACLs Information Disclosure Vulnerability – CVE-2007-2229||Cumulative Impact|
|Windows Vista||Moderate Information Disclosure||Moderate|
|Windows Vista x64 Edition||Moderate Information Disclosure||Moderate|
Permissive User Information Store ACLs Information Disclosure Vulnerability - CVE-2007-2229
There is an information disclosure vulnerability in Windows Vista that could allow non-privileged users to access local user information data stores including administrative passwords contained within the registry and local file system. The vulnerability could allow a local attacker to have access to user account data that could then be used in an attempt to gain full access to the affected system.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-2229.
Mitigating Factors for Permissive User Information Store ACLs Information Disclosure Vulnerability - CVE-2007-2229
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factor may be helpful in your situation:
An attacker must have valid logon credentials.
Workarounds for Permissive User Information Store ACLs Information Disclosure Vulnerability - CVE-2007-2229
We have not identified any workarounds for this vulnerability.
FAQ for Permissive User Information Store ACLs Information Disclosure Vulnerability - CVE-2007-2229
What is the scope of the vulnerability?
This is an information disclosure vulnerability. A local attacker who successfully exploited this vulnerability could use the information to gain valid logon credentials. An attacker using compromised logon credentials could then gain access to additional data available to other user accounts or potentially be used take complete control of an affected system.
What causes the vulnerability?
On Windows Vista, permissions on certain user information stores in the registry and local file system are set by default to a level that may allow a low-privileged users unnecessary access.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system, or access any data available to compromised user accounts.
How could an attacker exploit the vulnerability?
An attacker would have to logon locally to an affected system and identify the information data stores.
Could the vulnerability be exploited over the Internet?
No. This vulnerability can only be exploited by locally authenticated users with local access to the affected system.
What systems are primarily at risk from the vulnerability?
Any Windows Vista system. Windows Vista systems that have been upgraded from Windows XP may be at more risk because of additional information that is stored as a result of the upgrade process.
What does the update do?
The update addressees the vulnerability by removing unprivileged users’ access to the confidential information data stores contained in the local files system. The data stores are as a result restricted to users only with Administrator access.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch". Finally, security updates can be downloaded from the Windows Update Catalog. For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
Detection and Deployment Guidance
Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA visit Microsoft Baseline Security Analyzer Web site. The following table provides the MBSA detection summary for this security update.
|Software||MBSA 1.2.1||MBSA 2.0.1|
|Windows Vista||No||See Note for Windows Vista below|
|Windows Vista x64 Edition||No||See Note for Windows Vista below|
Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
|Product||SMS 2.0||SMS 2003|
|Windows Vista x64 Edition||No||Yes|
For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
Note for Windows Vista Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.
For more information about SMS, visit the SMS Web site.
Security Update Deployment
For information about the specific security update for your affected software, click the appropriate link:
Windows Vista (all versions)
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
|Inclusion in Future Service Packs||The update for this issue may be included in a future update rollup|
|Installing without user intervention||Windows Vista:
Windows6.0-kb 931213-x86-enu /quiet
|Installing without restarting||Windows Vista:
Windows6.0-kb 931213-x86-enu /norestart
|Further information||See the subsection, Detection and Deployment Tools and Guidance|
|Restart required||Yes, you must restart your system after you apply this security update|
|Removal Information||To remove this update, click Control Panel, click Security, then under Windows Update, click View installed updates and select from the list of updates.|
|File Information||See the subsection, File Information, in this section, for the full file manifest|
The English version of this security update has the 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 tool in Control Panel.
For all supported and affected 32-bit editions of Windows Vista:
For all supported and affected editions of Windows Vista x64:
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Windows hotfix. If you have previously installed a hotfix to update one of these files, the installer will apply the LDR version of this update. Otherwise, the installer will apply the GDR version of the update. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 934307.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
|/?, /h, /help||Displays help on supported switches.|
|/quiet||Suppresses the display of status or error messages.|
|/norestart||When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.|
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Removing the Update
To remove this update, use the Add or Remove Programs tool in Control Panel.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Microsoft thanks the following for working with us to help protect customers:
Robbie Sohlman for reporting the Permissive User Information Store ACLs Information Disclosure Vulnerability – (CVE-2007-2229).
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
- V1.0 (June 12, 2007): Bulletin published.
Built at 2014-04-18T13:49:36Z-07:00