__________________________________________________________
The U.S. Department of Energy
Computer Incident Advisory Capability
___ __ __ _ ___
/ | /_\ /
\___ __|__ / \ \___
__________________________________________________________
INFORMATION BULLETIN
Vulnerability in Microsoft Project
[Microsoft Security Bulletin (MS08-018)]
April 9, 2008 19:00 GMT Number S-253
[REVISED 10 Apr 2008]
[REVISED 17 Apr 2008]
[REVISED 30 Sep 2008]
______________________________________________________________________________
PROBLEM: A remote code execution vulnerability exists in the way
Microsoft Project handles specially crafted Project files.
PLATFORM: Project 2000 (all editions)
Project 2002 (all editions)
Project 2003 (all editions)
Storage Management Appliance (SMA) v2.1 software running on
Storage Management Appliance I, II, III
DAMAGE: Remote code execution.
SOLUTION: Upgrade to the appropriate version.
______________________________________________________________________________
VULNERABILITY The risk is MEDIUM. An attacker who successfully exploited this
ASSESSMENT: vulnerability could take complete control of an affected
system.
______________________________________________________________________________
CVSS 2 BASE SCORE: 6.4
TEMPORAL SCORE: 5.3
VECTOR: (AV:N/AC:L/Au:N/C:P/I:P/A:N/E:F/RL:OF/RC:C)
______________________________________________________________________________
LINKS:
CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/s-253.shtml
ORIGINAL BULLETIN: http://www.microsoft.com/technet/security/Bulletin/MS08-018.mspx
ADDITIONAL LINK: Visit Hewlett-Packard's Subscription Service for:
HPSBST02329 SSRT080048 rev.1
CVE: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=
CVE-2008-1088
______________________________________________________________________________
REVISION HISTORY:
04/10/2008 - revised S-253 to reflect changes Microsoft has made in MS08-018 where
they added Microsoft Project 2003 Service Pack 3 to the Non-Affected
Software table, to add a link to Microsoft Knowledge Base Article
950183 in Known Issues, and to add a section for Microsoft Project
2003 Servcie Pack 3 to the FAQ.
04/17/2008 - revised S-253 to reflect changes Microsoft has made in MS08-018 where they
added an entry to Update FAQ to describe additional security features
included for Microsoft Office 2003 Service Pack 2; updated Microsoft
Baseline Security Analyzer and Systems Management Server tables to match
the Affected Software Table; and to add a link to link to Hewlett-Packard's
Subscription Service for HPSBST02329 SSRT080048 rev. 1 for Storage
Management Appliance (SMA) v2.1 software running on Storage Management
Appliance I, II, III.
09/30/2008 - revised S-253 to reflect changes Microsoft has made in MS08-018 where they
added an entry to Update FAQ to Clarify why this update is Critical for
Project 2000 but only Important for all other affected versions of Project.
[***** Start Microsoft Security Bulletin (MS08-018) *****]
Microsoft Security Bulletin MS08-018 – Critical
Vulnerability in Microsoft Project Could Allow Remote Code Execution (950183)
Published: April 8, 2008 | Updated: September 10, 2008
Version: 1.3
General Information
Executive Summary
This security update resolves a privately reported vulnerability in Microsoft
Office Project that could allow remote code execution if a user opens a specially
crafted Project file. An attacker who successfully exploited this vulnerability
could take complete control of an affected system. An attacker could then install
programs; view, change, or delete data; or create new accounts with full user
rights. 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 security update is rated Critical for Microsoft Project 2000 Service Release
1 and rated Important for Microsoft Project 2002 Service Pack 1, and Microsoft
Office Project 2003 Service Pack 2. For more information, see the subsection,
Affected and Non-Affected Software, in this section.
This security update addresses this vulnerability by modifying the way that
Microsoft Project calculates the required memory allocation when opening Project.
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 apply the update immediately
Known Issues. Microsoft Knowledge Base Article 950183 documents the currently
known issues and recommended solutions that customers may experience when
installing this security update. When currently known issues and recommended
solutions pertain only to specific releases of this software, this article
provides links to further articles.
Top of section
Affected and Non-Affected Software
The following software 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
Office Software Maximum Security Impact Aggregate Severity Rating Bulletins
Replaced by this Update
Microsoft Project 2000 Service Release 1
(KB949043)
Remote Code Execution
Critical
None
Microsoft Project 2002 Service Pack 1
(KB949005)
Remote Code Execution
Important
None
Microsoft Project 2003 Service Pack 2
(KB948962)
Remote Code Execution
Important
None
Non-Affected Software
Office and Other Software
Microsoft Project Server 2003 Service Pack 3
Microsoft Project Server 2003
Microsoft Project Server 2003 Service Pack 3
Microsoft Project 2007
Microsoft Project 2007 Service Pack 1
Microsoft Project Portfolio Server 2007
Microsoft Project Server 2007
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
Affected Software Project Memory Validation Vulnerability CVE-2008-1088
Aggregate Severity Rating
Microsoft Project 2000 Service Release 1
Critical
Remote Code Execution
Critical
Microsoft Project 2002 Service Pack 1
Important
Remote Code Execution
Important
Microsoft Office Project 2003 Service Pack 2
Important
Remote Code Execution
Important
Top of section
Project Memory Validation Vulnerability - CVE-2008-1088
A remote code execution vulnerability exists in the way Microsoft Project handles
specially crafted Project files. An attacker could exploit the vulnerability by
sending a malformed file which could be included as an e-mail attachment, or
hosted on a specially crafted or compromised Web site.
If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of an
affected system. An attacker could then install programs; view, change, or delete
data; or create new accounts with full user rights. Users whose accounts are
configured to have fewer user rights on the system could be less affected than
users who operate with administrative user rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and
Exposures list, see CVE-2008-1088.
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. 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 from the Microsoft Download Center.
You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. 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.
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), and the Extended
Security Update Inventory Tool. 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.
The following table provides the MBSA detection summary for this security update.
Software MBSA 2.0.1
Office 2000 Service Pack 3
No
Office XP Service Pack 3
Yes
Office 2003 Service Pack 2
Yes
For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions.
Note For customers using legacy software not supported by MBSA 2.0.1, Microsoft
Update, and Windows Server Update Services: please visit Microsoft Baseline
Security Analyzer and reference the Legacy Product Support section on how to create
comprehensive security update detection with legacy tools.
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.
Software SMS 2.0 SMS 2003 with SUSFP SMS 2003 with ITMU SCCM 2007
Office 2000 Service Pack 3
Yes
Yes
No
No
Office XP Service Pack 3
Yes
Yes
Yes
Yes
Office 2003 Service Pack 2
Yes
Yes
Yes
Yes
For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security
Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also
Downloads for Systems Management Server 2.0.
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, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the
Microsoft Office Inventory Tool to detect required updates for Microsoft Office
applications. For more information about the Office Inventory Tool and other scanning
tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems
Management Server 2003.
System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates.
For more information about SCCM 2007 Software Update Management, visit System Center
Configuration Manager 2007.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary
list of monthly detection and deployment guidance articles.
Note If you have used an Administrative Installation Point (AIP) for deploying Office
2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if
you have updated the AIP from the original baseline. For more information, see the
Office Administrative Installation Point heading in this section.
Office Administrative Installation Point
If you installed your application from a server location, the server administrator must
update the server location with the administrative update and deploy that update to your
system.
• For supported versions of Microsoft Office 2000, see How to Create an Administrative
Installation Point. For more information about how to change the source for a
client system from an updated administrative installation point to an Office 2000
Service Pack 3 (SP3), see Microsoft Knowledge Base Article 932889.
Note If you plan to manage software updates centrally from an updated administrative
image, you can find more information in the article Updating Office 2000 Clients from
a Patched Administrative Image.
• For supported versions of Microsoft Office XP, see Creating an Administrative
Installation Point. For more information on how to change the source for a client
system from an updated administrative installation point to an Office XP original
baseline source, see Microsoft Knowledge Base Article 922665.
Note If you plan to manage software updates centrally from an updated
administrative image, you can find more information in the article Updating Office
XP Clients from a Patched Administrative Image.
• For supported versions of Microsoft Office 2003, see Creating an Administrative
Installation Point. For more information on how to change the source for a
client computer from an updated administrative installation point to an Office
2003 original baseline source or Service Pack 2 (SP2), see Microsoft Knowledge
Base Article 902349.
Note If you plan to manage software updates centrally from an updated
administrative image, you can find more information in the article Distributing
Office 2003 Product Updates.
Top of section
Security Update Deployment
Affected Software
For information about the specific security update for your affected software,
click the appropriate link:
* Project 2000 (all editions)
* Project 2002 (all editions)
* Project 2003 (all editions)
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
• National Cyber Security Center, The Republic of Korea for reporting the Project
Memory Validation Vulnerability - CVE-2008-1088.
Top of section
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.
Top of section
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.
Top of section
Revisions
• V1.0 (April 8, 2008): Bulletin published.
• V1.1 (April 9, 2008): Bulletin updated to add Microsoft Project 2003 Service
Pack 3 to the Non-Affected Software table, to add a link to Microsoft Knowledge
Base Article 950183 in Known Issues, and to add a section for Microsoft Project
2003 Service Pack 3 to the FAQ.
• V1.2 (April 16, 2008): Bulletin updated: Added entry to Update FAQ to describe
additional security features included for Microsoft Office 2003 Service Pack 2.
Updated Microsoft Baseline Security Analyzer and Systems Management Server tables
to match the Affected Software table.
• V1.3 (September 10, 2008): Bulletin updated: Added entry to Update FAQ to clarify
why this update is Critical for Project 2000 but only Important for all other
affected versions of Project.
[***** End Microsoft Security Bulletin (MS08-018) *****]
_______________________________________________________________________________
CIAC wishes to acknowledge the contributions of Microsoft for the
information contained in this bulletin.
_______________________________________________________________________________
CIAC, the Computer Incident Advisory Capability, is the computer
security incident response team for the U.S. Department of Energy
(DOE) and the emergency backup response team for the National
Institutes of Health (NIH). CIAC is located at the Lawrence Livermore
National Laboratory in Livermore, California. CIAC is also a founding
member of FIRST, the Forum of Incident Response and Security Teams, a
global organization established to foster cooperation and coordination
among computer security teams worldwide.
CIAC services are available to DOE, DOE contractors, and the NIH. CIAC
can be contacted at:
Voice: +1 925-422-8193 (7x24)
FAX: +1 925-423-8002
STU-III: +1 925-423-2604
E-mail: ciac@ciac.org
Previous CIAC notices, anti-virus software, and other information are
available from the CIAC Computer Security Archive.
World Wide Web: http://www.ciac.org/
Anonymous FTP: ftp.ciac.org
PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing
communities receive CIAC bulletins. If you are not part of these
communities, please contact your agency's response team to report
incidents. Your agency's team will coordinate with CIAC. The Forum of
Incident Response and Security Teams (FIRST) is a world-wide
organization. A list of FIRST member organizations and their
constituencies can be obtained via WWW at http://www.first.org/.
This document was prepared as an account of work sponsored by an
agency of the United States Government. Neither the United States
Government nor the University of California nor any of their
employees, makes any warranty, express or implied, or assumes any
legal liability or responsibility for the accuracy, completeness, or
usefulness of any information, apparatus, product, or process
disclosed, or represents that its use would not infringe privately
owned rights. Reference herein to any specific commercial products,
process, or service by trade name, trademark, manufacturer, or
otherwise, does not necessarily constitute or imply its endorsement,
recommendation or favoring by the United States Government or the
University of California. The views and opinions of authors expressed
herein do not necessarily state or reflect those of the United States
Government or the University of California, and shall not be used for
advertising or product endorsement purposes.
LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC)
S-213: Nukedit 'email' Parameter Vulnerability
S-214: SurgeMail and WebMail 'Page' Command Vulnerability
S-215: Symantec Backup Exec Scheduler ActiveX Control Multiple Vulnerabilities
S-216: Juniper Networks Secure Access 2000 'rdremediate.cgi' Vulnerability
S-217: Drupal Multiple HTML Vulnerabilities
S-218: gd Security Update
S-219: Juniper Networks Secure Access 2000 Web Root Path Vulnerability
S-220: PHP-Nuke My_eGallery Module 'gid' Parameter Vulnerability
S-221: Learn2 STRunner ActiveX Control Vulnerabilities
S-222: Evolution Security Update