Security Bulletin

Microsoft Security Bulletin MS07-055 - Critical

Vulnerability in Kodak Image Viewer Could Allow Remote Code Execution (923810)

Published: October 09, 2007 | Updated: October 17, 2007

Version: 1.1

General Information

Executive Summary

This critical security update resolves a privately reported vulnerability. A remote code execution vulnerability exists in the way that the Kodak Image Viewer, formerly known as Wang Image Viewer, handles specially crafted images files. The vulnerability could allow an attacker to remotely execute code on the affected system. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This vulnerability exists only on systems running Windows 2000. However, systems running supported 32-bit editions of Windows XP and Windows Server 2003 may also be affected if upgraded from Windows 2000. This is a critical security update for Windows 2000 Service Pack 4, 32-bit editions of Windows XP Service Pack 2, and supported 32-bit editions of Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

This security update addresses the vulnerability by deprecating file types that are no longer supported as well as by improving the way that the Kodak image viewer handles specially crafted file types. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update immediately.

Known Issues. None.

Affected and Non-Affected Software

The software listed here have 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.

Affected Software

Operating System Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by This Update
Microsoft Windows 2000 Service Pack 4 Remote Code Execution Critical None
Windows XP Service Pack 2 Remote Code Execution Critical None
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Remote Code Execution Critical None

Note Supported editions of Windows XP and Windows Server 2003 are not vulnerable unless upgraded from Windows 2000.

Non-Affected Software

Operating System
Windows XP x64 Edition and Windows XP x64 Edition 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
Windows Vista
Windows Vista x64 Edition

I am running Windows XP or Windows Server 2003 but do not have Kodak image viewer installed, am I vulnerable?
No, initial or full installations of Windows XP and Windows 2003 are not vulnerable. Systems running Windows XP and Windows Server 2003 are only vulnerable if they were upgraded from Windows 2000.

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 have 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.

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Kodak Image Viewer Remote Code Execution Vulnerability – CVE-2007-2217 Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 Critical Remote Code Execution Critical
Windows XP Service Pack 2 Critical Remote Code Execution Critical
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Critical Remote Code Execution Critical
Kodak Image Viewer Remote Code Execution Vulnerability – CVE-2007-2217 ---------------------------------------------------------------------- A remote code execution vulnerability exists in the way that the Kodak Image Viewer in Windows handles specially crafted image files. An attacker could exploit the vulnerability by constructing a specially crafted image that could potentially allow remote code execution if a user visited a Web site, viewed a specially crafted e-mail message, or opened an e-mail attachment. An attacker who successfully exploited this vulnerability could take complete control of an affected system. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2007-2217](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2007-2217). #### Mitigating Factors for Kodak image Viewer Remote Code Execution Vulnerability – CVE-2007-2217 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 factors may be helpful in your situation: - Systems running Windows XP and Windows Server 2003 are only vulnerable if they were upgraded from Windows 2000. - When ‘Use Windows Classic Folders’ is enabled for viewing files, users are protected from shell-based attacks - Office 2003 installs an image viewer application that takes over the file association, and is not vulnerable to this vulnerability. - In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site. - An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. #### Workarounds for Kodak image Viewer Remote Code Execution Vulnerability – CVE-2007-2217 Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality: - **Read e-mail messages in plain text format to help protect yourself from the HTML e-mail attack vector** You can help protect yourself against this vulnerability by changing your e-mail settings to read e-mail messages in plain text using Outlook 2002 and later, Outlook Express 6 and later, or Windows Mail. For information in Outlook, search “plain text” in Help and review “Read messages in plain text.” In Outlook Express, search “plain text” in Help and review “Reducing your risk of getting e-mail viruses.” In Windows Mail, search “plain text” in Help and review “Security and privacy in Windows Mail.” **Impact of workaround:** E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally: - The changes are applied to the preview pane and to open messages. - Pictures become attachments so that they are not lost. - Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly. - **Modify the access control list on oieng400.dll** To modify the Access Control List (ACL) on oieng400.dll to be more restrictive, follow these steps: 1. Log on as a user with administrator privileges. 2. Click **Start**, click **Run**, type **cmd**, and then click **OK**. 3. Document the current ACLs that are on the file (including inheritance settings) for future reference in case you have to undo this modification. To view the ACLs, type the following: **cacls “C:\\winnt\\system32\\oieng400.dll”** 4. To deny the “everyone” group access to the file, type the following command at a command prompt: **cacls “C:\\winnt\\system32\\oieng400.dll”** /**E /D Everyone** **Impact of workaround:** Kodak Image Viewer will not open. **How to undo the workaround:** Restore the ACL that was documented in step 3 of this workaround. #### FAQ for Kodak image Viewer Remote Code Execution Vulnerability – CVE-2007-2217 **What is the scope of the vulnerability?** This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs or view, change, or delete data. **What causes the vulnerability?** The Windows Kodak image Viewer improperly parses specially crafted image files. As a result, memory may be corrupted in such a way that an attacker could execute arbitrary code in the context of the logged-on user. **What might an attacker use the vulnerability to do?** An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. **How could an attacker exploit the vulnerability?** An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then convince a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems. **What systems are primarily at risk from the vulnerability?** This vulnerability requires that a user view or open a specially crafted image file. Any system where applications use the affected Kodak image Viewer library to view or open image files are at risk. **What does the update do?** The update removes the vulnerability by improving the way that the Kodak image viewer handles specially crafted file types. **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. ### Update Information Detection and Deployment Tools and Guidance ------------------------------------------- Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the [TechNet Update Management Center](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747), [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130), and [Office Update](http://go.microsoft.com/fwlink/?linkid=21135). Security updates are also available at the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). You can find them most easily by doing a keyword search for "security\_patch." Finally, security updates can be downloaded from the [Microsoft Update Catalog](http://go.microsoft.com/fwlink/?linkid=96155). The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the [Microsoft Update Catalog FAQ](http://go.microsoft.com/fwlink/?linkid=97900). **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](http://support.microsoft.com/kb/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](http://go.microsoft.com/fwlink/?linkid=21134). The following table provides the MBSA detection summary for this security update. | Software | MBSA 1.2.1 | MBSA 2.0.1 | |-------------------------------------------------------------------------------------|------------|------------| | Microsoft Windows 2000 Service Pack 4 | Yes | Yes | | Windows XP Service Pack 2 | Yes | Yes | | Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2 | Yes | Yes | For more information about MBSA, visit the [MBSA Web site](http://go.microsoft.com/fwlink/?linkid=21134). For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see [Microsoft Knowledge Base Article 895660](http://support.microsoft.com/kb/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](http://go.microsoft.com/fwlink/?linkid=50120). **Systems Management Server** The following table provides the SMS detection and deployment summary for this security update. | Software | SMS 2.0 | SMS 2003 | |-------------------------------------------------------------------------------------|---------|----------| | Microsoft Windows 2000 Service Pack 4 | Yes | Yes | | Windows XP Service Pack 2 | Yes | Yes | | Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2 | Yes | Yes | SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect. 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](http://support.microsoft.com/kb/894154/). For more information about the limitations of SUIT, see [Microsoft Knowledge Base Article 306460](http://support.microsoft.com/kb/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](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, visit the following [Microsoft Web site](http://go.microsoft.com/fwlink/?linkid=72181). SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about SMS, visit the [SMS Web site](http://go.microsoft.com/fwlink/?linkid=21158). Security Update Deployment -------------------------- **Affected Software** For information about the specific security update for your affected software, click the appropriate link: #### Windows 2000 (all editions) **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 | Windows2000-KB923810-x86-enu /quiet | | Installing without restarting | Windows2000-KB923810-x86-enu /norestart | | Update log file | KB923810.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** | Use Add or Remove Programs tool in Control Panel or the SP uninstall tool at %Windir%\\$NTUninstallKB9238109$\\Spuninst | | **File Information** | See the next subsection, **File Information**, for the full file manifest | | **Registry Key Verification** | HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows 2000\\SP5\\KB923810\\Filelist | #### 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 editions of Windows 2000: | File Name | Version | Date | Time | Size | |--------------|---------------|-------------|-------|-----------| | jpeg2x32.dll | 5.0.2195.7134 | 17-Aug-2007 | 06:48 | 39,184 | | kodakimg.exe | 5.0.2195.7136 | 11-May-2007 | 07:41 | 524,560 | | kodakprv.exe | 5.0.2195.7136 | 11-May-2007 | 07:42 | 73,488 | | oieng400.dll | 5.0.2195.7144 | 17-Aug-2007 | 06:48 | 448,272 | | Sp3res.dll | 5.0.2195.7136 | 28-May-2007 | 07:56 | 6,258,688 | | tifflt.dll | 5.0.3900.7134 | 17-Aug-2007 | 06:48 | 33,552 | **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](http://support.microsoft.com/gp/lifesupsps). For more information on the support lifecycle policy, see [Microsoft Support Lifecycle](http://support.microsoft.com/lifecycle/). #### 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. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see [Microsoft Knowledge Base Article 824994](http://support.microsoft.com/kb/824994). For more information about the installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951). For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe 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
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**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.

Windows XP (all editions)

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 will be included in a future service pack or update rollup
Deployment
Installing without user intervention WindowsXP-KB923810-x86-enu /quiet
Installing without restarting WindowsXP-KB923810-x86-enu /norestart
Update log file KB923810.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 Use Add or Remove Programs tool in Control Panel or the SP uninstall tool at %Windir%\$NTUninstallKB9238109$\Spuninst
File Information See the next subsection, File Information, for the full file manifest
Registry Key Verification HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB923810\Filelist

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 editions of Windows XP:

File Name Version Date Time Size Folder
kodakimg.exe 5.0.2195.7138 07-Sep-2007 10:04 524,317 SP2QFE
kodakprv.exe 5.0.2195.7138 07-Sep-2007 10:04 73,245 SP2QFE
oieng400.dll 5.0.2195.7146 07-Sep-2007 17:57 448,029 SP2QFE
tifflt.dll 5.0.3900.7136 07-Sep-2007 1 7:57 33,307 SP2QFE
xpsp3res.dll 5.1.2600.3158 01-Jul-2007 07:25 350,720 SP2QFE

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.

Deployment Information

Installing the Update

This update will only install on your computer if you have upgraded your operating system from Microsoft Windows 2000. If you have a computer which has never had Windows 2000, you are not affected by this vulnerability.

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.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

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
**/integrate:path** Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
**/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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe 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
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**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.

Windows Server 2003 (all editions)

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 will be included in a future service pack or update rollup
Deployment
Installing without user intervention WindowsServer2003-KB923810-x86-enu /quiet
Installing without restarting WindowsServer2003-KB923810-x86-enu /norestart
Update log file KB92810.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 Use Add or Remove Programs tool in Control Panel or the SP uninstall tool at %Windir%\$NTUninstallKB9238109$\Spuninst
File Information See the next subsection, File Information, for the full file manifest
Registry Key Verification HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB923810\Filelist

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

File Name Version Date Time Size Folder
jpeg2x32.dll 5.0.2195.7138 10-Sep-2007 17:31 38,941 SP1QFE
kodakimg.exe 5.0.2195.7140 10-Sep-2007 07:51 524,317 SP1QFE
kodakprv.exe 5.0.2195.7140 10-Sep-2007 07:51 73,245 SP1QFE
oieng400.dll 5.0.2195.7148 10-Sep-2007 17:31 448,029 SP1QFE
tifflt.dll 5.0.3900.7138 10-Sep-2007 17:31 33,307 SP1QFE
w03a2409.dll 5.2.3790.2957 18-Jun-2007 04:31 28,672 SP1QFE
jpeg2x32.dll 5.0.2195.7139 10-Sep-2007 17:37 38,941 SP2QFE
kodakimg.exe 5.0.2195.7141 10-Sep-2007 10:18 524,317 SP2QFE
kodakprv.exe 5.0.2195.7141 10-Sep-2007 10:18 73,245 SP2QFE
oieng400.dll 5.0.2195.7149 10-Sep-2007 17:37 448,029 SP2QFE
tifflt.dll 5.0.3900.7139 10-Sep-2007 17:37 33,307 SP2QFE
w03a3409.dll 5.2.3790.4107 29-Jun-2007 07:28 13,824 SP2QFE

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.

Deployment Information

Installing the Update

This update will only install on your computer if you have upgraded your operating system from Microsoft Windows 2000. If you have a computer which has never had Windows 2000, you are not affected by this vulnerability.

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

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
**/integrate:path** Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
**/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 many of 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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe 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
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**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.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

  • Cu Fang for reporting the Kodak Image Viewer Remote Code Execution Vulnerability – CVE-2007-2217.
  • Rita Schappler of Global 360 for working with us on the Kodak Image Viewer Remote Code Execution Vulnerability – CVE-2007-2217.

Support

  • 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.

Disclaimer

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.

Revisions

  • V1.0 (October 9, 2007): Bulletin published.
  • V1.1 (October 17, 2007): Bulletin updated to include Windows XP x64 Edition among non-affected software.

Built at 2014-04-18T13:49:36Z-07:00