Microsoft Security Bulletin MS07-053 - Important

What are the known issues that customers may experience when they install this security update? 
Microsoft Knowledge Base Article 939778 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

I am using an older release 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 releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases 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 software releases, 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.

A vulnerability exists in Windows Services for UNIX 3.0, Windows Services for UNIX 3.5, and Subsystem for UNIX-based Applications where running certain setuid binary files could allow an attacker to gain elevation of privilege. An attacker who successfully exploited this vulnerability could gain elevation of privilege.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-3036.

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state that could reduce the severity of exploitation of vulnerability. The following mitigating factors may be helpful in your situation:

•

Default configurations of Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, and Windows Server 2003 Service Pack 2 do not include Windows Services for UNIX 3.0 and Windows Services for UNIX 3.5. Windows Services for UNIX 3.0 and Windows Services for UNIX 3.5. may be optionally installed on Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, and Windows Server 2003 Service Pack 2. Windows Vista and Windows Server 2003 do not have Subsystem for UNIX-based Applications enabled by default. Subsystem for UNIX-based Applications is an optional Windows component for Windows Vista and Windows Server 2003.

Top of section

Microsoft has not identified any workarounds for this vulnerability.

Top of section

What is the scope of the vulnerability? 
An elevation of privilege vulnerability exists in Windows Services for UNIX 3.0, Windows Services for UNIX 3.5, and Subsystem for UNIX-based Applications where running certain setuid binary files that could allow an attacker to gain elevation of privilege. An attacker who successfully exploited this vulnerability could gain elevation of privilege. An attacker could then install programs or view, change, or delete data.

What causes the vulnerability? 
Windows Services for UNIX 3.0, Windows Services for UNIX 3.5, and Subsystem for UNIX-based Applications incorrectly handles setuid binary files.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain elevation of privilege on an affected system. Users whose accounts are configured to have fewer user rights on the guest operating system are not less impacted than users who operate with administrative user rights on the guest operating system.

How could an attacker exploit the vulnerability? 
An attacker would have to log on locally to an affected system and run certain setuid binary files. Or an attacked would have to convince users to run certain setuid binary files.

What is setuid? 
Users of client computers can set the setuid (set-user-identifier-on-execution) bit for a file. An executable file which has the setuid bit set will execute under the user ID of the file's owner, not the user ID of the user who is executing the file.

What systems are primarily at risk from the vulnerability? 
Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, and Windows Server 2003 Service Pack where Windows Services for UNIX 3.0 or Windows Services for UNIX 3.5 is installed. Windows Server 2003 R2 as an extension of Windows Server 2003. Windows Vista where Subsystem for UNIX-based Applications is enabled.

What does the update do? 
The update removes the vulnerability by correctly handling connection credentials for setuid binary files.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
Yes. This vulnerability has been publicly disclosed with limited distribution.

Top of section

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 and Enterprise Update Scan Tool (EST)

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.

The following table provides the MBSA and EST detection summary for this security update.

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.

For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

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.

The Security Update Inventory Tool for SMS 2.0 and SMS 2003 uses the MBSA 1.2.1 engine to detect security updates and therefore has the same limitations that are listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

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.

The SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update. ITMU uses MBSA 2.0.1 and therefore has the same limitations that are listed earlier in this bulletin related to programs that MBSA 2.0.1 does not detect. 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.

Note for ITMU: Subsystem for Unix applications on Windows Server 2003 is a part of the Windows OS and update detection for this component is supported by MBSA 2.0.1. SMS 2003 can detect and deploy this update using ITMU.

Note for EST: Services for Unix 3.0 and Services for Unix 3.5 are full-featured add-ons to Windows 2000, Windows XP, Windows Vista and Windows Server 2003. MBSA 2.0.1 does not support update detection on these applications. The Enterprise Scan Tool for September 2007 is provided to detect the required update for MS07-053 on all supported platforms. Update deployment can be addressed by SMS as a standard software distribution.

The Extended Security Update Inventory Tool for SMS 2.0 and SMS 2003 uses the same engine as the EST and can be used by SMS to detect updates for products not supported by MBSA. The current version of this tool provides cumulative support for most updates not detected by MBSA starting with MS04-028. If a previous version of the Extended Security Update Inventory Tool has been installed on SMS, it will need to be upgraded with the current version of the tool to enable detection of MS07-053.

For more information about SMS, visit the SMS Web site.

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Reference Table

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
Deployment
Installing without user intervention	For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB939778-x86-ENU.exe /quiet
	For all supported 64-bit editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB939778-x64-ENU.exe /quiet
Installing without restarting	For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB939778-x86-ENU.exe /norestart
	For all supported 64-bit editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB939778-x64-ENU.exe /norestart
Update log file	KB939778.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update.
Hotpatching	Not applicable
Removal Information	To remove this security update, use the Add or Remove Programs tool in Control Panel.
File Information	See the heading, File Information, below for the full file manifest.
Registry Key Verification	For all supported editions of Windows Server 2003: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB939778

File Information

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 32-bit editions of Windows Server 2003:

File Name	Version	Date	Time	Size	Folder
posix.exe	9.0.3790.2983	27-Jul-2007	18:53	53,248	SP1GDR
psxdll.dll	9.0.3790.2983	30-Jul-2007	21:44	248,832	SP1GDR
psxdllsvr.dll	9.0.3790.2983	30-Jul-2007	21:44	299,008	SP1GDR
psxdllthunkedsvr.dll	9.0.3790.2983	30-Jul-2007	21:44	315,904	SP1GDR
psxss.exe	9.0.3790.2983	27-Jul-2007	18:53	566,272	SP1GDR
posix.exe	9.0.3790.2983	27-Jul-2007	18:56	56,320	SP1QFE
psxdll.dll	9.0.3790.2983	30-Jul-2007	21:20	248,832	SP1QFE
psxdllsvr.dll	9.0.3790.2983	30-Jul-2007	21:20	299,008	SP1QFE
psxss.exe	9.0.3790.2983	27-Jul-2007	18:56	570,368	SP1QFE
posix.exe	9.0.3790.4125	27-Jul-2007	20:39	53,248	SP2GDR
psxdll.dll	9.0.3790.4125	30-Jul-2007	21:50	249,344	SP2GDR
psxdllsvr.dll	9.0.3790.4125	30-Jul-2007	22:25	299,520	SP2GDR
psxdllthunkedsvr.dll	9.0.3790.4125	30-Jul-2007	21:50	315,904	SP2GDR
psxss.exe	9.0.3790.4125	28-Jul-2007	01:04	566,784	SP2GDR
posix.exe	9.0.3790.4125	27-Jul-2007	20:36	56,320	SP2QFE
psxdll.dll	9.0.3790.4125	30-Jul-2007	21:15	248,832	SP2QFE
psxdllsvr.dll	9.0.3790.4125	30-Jul-2007	21:15	299,008	SP2QFE
psxss.exe	9.0.3790.4125	27-Jul-2007	20:36	570,880	SP2QFE

For all supported 64-bit editions of Windows Server 2003:

File Name	Version	Date	Time	Size	CPU	Folder
posix.exe	9.0.3790.2983	30-Jul-2007	22:28	65,536	X64	SP1GDR
psxdll.dll	9.0.3790.2983	30-Jul-2007	22:28	286,208	X64	SP1GDR
psxdllsvr.dll	9.0.3790.2983	30-Jul-2007	22:28	333,824	X64	SP1GDR
psxss.exe	9.0.3790.2983	30-Jul-2007	22:28	776,704	X64	SP1GDR
Wpsxdllthunkedsvr.dll	9.0.3790.2983	30-Jul-2007	22:28	315,904	X86	SP1GDR\wow
wpsxdll_thunked.dll	9.0.3790.2983	30-Jul-2007	22:28	265,728	X86	SP1GDR\wow
posix.exe	9.0.3790.2983	30-Jul-2007	22:28	68,608	X64	SP1QFE
psxdll.dll	9.0.3790.2983	30-Jul-2007	22:28	286,208	X64	SP1QFE
psxdllsvr.dll	9.0.3790.2983	30-Jul-2007	22:28	334,336	X64	SP1QFE
psxss.exe	9.0.3790.2983	30-Jul-2007	22:28	780,288	X64	SP1QFE
Wpsxdllthunkedsvr.dll	9.0.3790.2983	30-Jul-2007	22:28	315,904	X86	SP1QFE\wow
wpsxdll_thunked.dll	9.0.3790.2983	30-Jul-2007	22:28	265,728	X86	SP1QFE\wow
posix.exe	9.0.3790.4125	30-Jul-2007	22:32	65,536	X64	SP2GDR
psxdll.dll	9.0.3790.4125	30-Jul-2007	22:32	286,720	X64	SP2GDR
psxdllsvr.dll	9.0.3790.4125	30-Jul-2007	22:32	334,336	X64	SP2GDR
psxss.exe	9.0.3790.4125	30-Jul-2007	22:32	776,704	X64	SP2GDR
Wpsxdllthunkedsvr.dll	9.0.3790.4125	30-Jul-2007	22:32	315,904	X86	SP2GDR\wow
wpsxdll_thunked.dll	9.0.3790.4125	30-Jul-2007	22:32	265,728	X86	SP2GDR\wow
posix.exe	9.0.3790.4125	30-Jul-2007	22:28	68,608	X64	SP2QFE
psxdll.dll	9.0.3790.4125	30-Jul-2007	22:28	286,208	X64	SP2QFE
psxdllsvr.dll	9.0.3790.4125	30-Jul-2007	22:28	334,336	X64	SP2QFE
psxss.exe	9.0.3790.4125	30-Jul-2007	22:28	780,800	X64	SP2QFE
Wpsxdllthunkedsvr.dll	9.0.3790.4125	30-Jul-2007	22:28	315,904	X86	SP2QFE\wow
wpsxdll_thunked.dll	9.0.3790.4125	30-Jul-2007	22:28	265,728	X86	SP2QFE\wow

Note For a complete list of supported versions and editions, 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.

Top of section

Deployment Information

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 Microsoft hotfix.

For more information about the 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.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem	Overwrites OEM files without prompting
/nobackup	Does not back up files needed for uninstall
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files
/extract[:path]	Extracts files without starting the Setup program
/ER	Enables extended error reporting
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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.

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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

1.	Click Start, and then click Search.
2.	In the Search Results pane, click All files and folders under Search Companion.
3.	In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4.	In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
5.	On the Version tab, determine the version of the file that is installed on your system 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.

•	Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Reference Table

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
Deployment
Installing without user intervention	For all supported 32-bit editions of Windows Vista: Windows6.0-KB939778-x86.msu /quiet
	For all supported 64-bit editions of Windows Vista: Windows6.0-KB939778-x64.msu /quiet
Installing without restarting	For all supported 32-bit editions of Windows Vista: Windows6.0-KB939778-x86.msu /norestart
	For all supported 64-bit editions of Windows Vista: Windows6.0-KB939778-x64.msu /norestart
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update.
Hotpatching	Not applicable
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 heading, File Information, below for the full file manifest.
Registry Key Verification	Note: A registry key does not exist to validate the presence of this patch. To detect the presence of the patch use Windows Management Instrumentation (WMI).

File Information

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 32-bit editions of Windows Vista:

File Name	Version	Date	Time	Size	Folder
posix.exe	6.0.6000.16543	14-Aug-2007	09:13	76,288	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
posixsscom.dll	6.0.6000.16543	14-Aug-2007	09:15	5,632	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
psxdll.dll	6.0.6000.16543	14-Aug-2007	09:15	294,400	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
psxdllsvr.dll	6.0.6000.16543	14-Aug-2007	09:15	343,552	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
psxdrv.sys	6.0.6000.16543	14-Aug-2007	07:59	8,704	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
psxrun.exe	6.0.6000.16543	14-Aug-2007	09:13	40,960	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
psxss.exe	6.0.6000.16543	14-Aug-2007	09:13	648,704	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
suagc.exe	6.0.6000.16543	14-Aug-2007	09:13	7,680	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
suares.dll	6.0.6000.16543	14-Aug-2007	06:17	2,048	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_71d9d867f2e6c98a
posix.exe	6.0.6000.20660	14-Aug-2007	08:08	76,288	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
posixsscom.dll	6.0.6000.20660	14-Aug-2007	09:23	5,632	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
psxdll.dll	6.0.6000.20660	14-Aug-2007	09:23	294,400	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
psxdllsvr.dll	6.0.6000.20660	14-Aug-2007	09:23	343,552	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
psxdrv.sys	6.0.6000.20660	14-Aug-2007	08:08	8,704	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
psxrun.exe	6.0.6000.20660	14-Aug-2007	08:08	40,960	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
psxss.exe	6.0.6000.20660	14-Aug-2007	08:09	648,704	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
suagc.exe	6.0.6000.20660	14-Aug-2007	08:08	7,680	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531
suares.dll	6.0.6000.20660	14-Aug-2007	06:21	2,048	Windows6.0-KB939778-x86\x86_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_724ad47d0c175531

For all supported 64-bit editions of Windows Vista:

File Name	Version	Date	Time	Size	CPU	Folder
posix.exe	6.0.6000.16543	14-Aug-2007	12:15	83,968	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
psxdll.dll	6.0.6000.16543	14-Aug-2007	12:15	311,808	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
psxdllsvr.dll	6.0.6000.16543	14-Aug-2007	12:15	360,448	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
psxdrv.sys	6.0.6000.16543	14-Aug-2007	08:21	9,728	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
psxrun.exe	6.0.6000.16543	14-Aug-2007	12:15	44,544	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
psxss.exe	6.0.6000.16543	14-Aug-2007	12:15	838,144	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
suagc.exe	6.0.6000.16543	14-Aug-2007	12:15	8,704	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
suares.dll	6.0.6000.16543	14-Aug-2007	06:16	2,048	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.16543_none_cdf873ebab443ac0
posix.exe	6.0.6000.20660	14-Aug-2007	08:17	83,968	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667
psxdll.dll	6.0.6000.20660	14-Aug-2007	11:39	311,808	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667
psxdllsvr.dll	6.0.6000.20660	14-Aug-2007	11:39	360,448	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667
psxdrv.sys	6.0.6000.20660	14-Aug-2007	08:17	9,728	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667
psxrun.exe	6.0.6000.20660	14-Aug-2007	08:17	44,544	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667
psxss.exe	6.0.6000.20660	14-Aug-2007	08:18	838,144	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667
suagc.exe	6.0.6000.20660	14-Aug-2007	08:17	8,704	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667
suares.dll	6.0.6000.20660	14-Aug-2007	06:15	2,048	X64	Windows6.0-KB939778-x64\amd64_subsystem-for-unix-based-applications_31bf3856ad364e35_6.0.6000.20660_none_ce697000c474c667

Note For a complete list of supported versions and editions, 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.

Top of section

Deployment Information

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 Microsoft hotfix.

For more information about the 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.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem	Overwrites OEM files without prompting
/nobackup	Does not back up files needed for uninstall
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files
/extract[:path]	Extracts files without starting the Setup program
/ER	Enables extended error reporting
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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.

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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

1.	Click Start, and then click Search.
2.	In the Search Results pane, click All files and folders under Search Companion.
3.	In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4.	In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
5.	On the Version tab, determine the version of the file that is installed on your system 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.

Top of section

Top of section

Reference Table

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
Deployment
Installing without user intervention	For Windows Services for UNIX 3.0 on Windows 2000 Service Pack 4, on Windows XP Service Pack 2, on Windows Server 2003 Service Pack 1, and on Windows Server 2003 Service Pack 2: SFU3-KB939778-X86-ENU.exe /Q
	For Windows Services for UNIX 3.5 on Windows 2000 Service Pack 4, on Windows XP Service Pack 2, on Windows Server 2003 Service Pack 1, and on Windows Server 2003 Service Pack 2: SFU35-KB939778-X86-ENU.exe /Q
Installing without restarting	For Windows Services for UNIX 3.0 on Windows 2000 Service Pack 4, on Windows XP Service Pack 2, on Windows Server 2003 Service Pack 1, and on Windows Server 2003 Service Pack 2: SFU3-KB939778-X86-ENU.exe /Z
	For Windows Services for UNIX 3.5 on Windows 2000 Service Pack 4, on Windows XP Service Pack 2, on Windows Server 2003 Service Pack 1, and on Windows Server 2003 Service Pack 2: SFU35-KB939778-X86-ENU.exe /Z
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update.
Hotpatching	Not applicable
Removal Information	To remove this security update, use the Add or Remove Programs tool in Control Panel.
File Information	See the heading, File Information, below for the full file manifest.
Registry Key Verification	For Windows Services for UNIX 3.0 on Windows 2000 Service Pack 4, and Windows Services for UNIX 3.0 on Windows XP Service Pack 2, and Windows Services for UNIX 3.0 on Windows Server 2003 Service Pack 1, and Windows Services for UNIX 3.0 on Windows Server 2003 Service Pack 2: HKLM\SOFTWARE\Microsoft\Updates\Microsoft Services for UNIX\KB939778\PackageVersion
	For Windows Services for UNIX 3.5 on Windows 2000 Service Pack 4, and Windows Services for UNIX 3.5 on Windows XP Service Pack 2, and Windows Services for UNIX 3.5 on Windows 2000 on Windows Server 2003 Service Pack 1, and Windows Services for UNIX 3.5 on Windows 2003 Service Pack 2: HKLM\SOFTWARE\Microsoft\Updates\Microsoft Services for UNIX\KB939778\PackageVersion

File Information

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 Windows Services for UNIX 3.0 on Windows 2000 Service Pack 4, on Windows XP Service Pack 2, on Windows Server 2003 Service Pack 1, and on Windows Server 2003 Service Pack 2:

File Name	Version	Date	Time	Size
Posix.exe	7.0.1701.46	30-Jul-2007	13:14	129,024
Psxdll.dll	7.0.1701.46	30-Jul-2007	13:14	146,432
Psxrun.exe	7.0.1701.46	30-Jul-200	13:14	103,424
Psxss.exe	7.0.1701.46	30-Jul-2007	13:14	670,208

For Windows Services for UNIX 3.5 on Windows 2000 Service Pack 4, on Windows XP Service Pack 2, on Windows Server 2003 Service Pack 1, and on Windows Server 2003 Service Pack 2:

File Name	Version	Date	Time	Size
Posix.exe	8.0.1969.58	02-Jul-2007	13:19	130,048
Psxdll.dll	8.0.1969.58	02-Jul-2007	13:19	345,088
Psxrun.exe	8.0.1969.58	02-Jul-2007	13:19	104,448
Psxss.exe	8.0.1969.58	02-Jul-2007	13:19	781,312

Note For a complete list of supported versions and editions, 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.

Top of section

Deployment Information

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 Microsoft hotfix.

For more information about the 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.

This security update supports the following setup switches.

Supported Hotfix.exe Security Update Installation Switches
Switch	Description
/y	Perform removal (only with /m or /q)
/f	Force programs to quit during the shutdown process
/n	Do not create an Uninstall folder
/z	Do not restart when the update finishes
/q	Use Quiet or Unattended mode without a user interface (this switch is a superset of /m)
/m	Use Unattended mode with a user interface
/l	List the installed hotfixes

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.

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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

1.	Click Start, and then click Search.
2.	In the Search Results pane, click All files and folders under Search Companion.
3.	In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4.	In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
5.	On the Version tab, determine the version of the file that is installed on your system 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.

•	Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section