Microsoft Publisher .pub file malformed string code execution
| publisher-pub-code-execution (28648) |  High Risk |
Description:
Microsoft Publisher could allow a remote attacker to execute arbitrary code on the system, caused by a memory corruption vulnerability that could occur when parsing Publisher (.pub) files containing malformed strings. A remote attacker could exploit this vulnerability to execute arbitrary code and gain complete control of an affected system, if the attacker could persuade the victim to open a malicious .pub file, either by hosting the file on a Web site or sending it to a victim as an email attachment.
*CVSS:
| Base Score: | 8 |
| Access Vector: | Remote |
| Access Complexity: | High |
| Authentication: | Not Required |
| Confidentiality Impact: | Complete |
| Integrity Impact: | Complete |
| Availability Impact: | Complete |
| Temporal Score: | 5.6 |
| Exploitability: | Unproven |
| Remediation Level: | Official-Fix |
| Report Confidence: | Uncorroborated |
Consequences:
Gain Access
Remedy:
Apply the appropriate patch for your system, as listed in the latest Microsoft Security Bulletin. See References.
— OR —
Use Microsoft Automatic Update if it is supported by your operating system. The original bulletin issued by Microsoft has been superseded.
References:
- Full-Disclosure Mailing List, Tue Sep 12 2006 - 15:07:32 CDT: Computer Terrorism (UK) :: Incident Response Centre - Microsoft Publisher Font Parsing Vulnerability.
- Microsoft Security Bulletin MS06-054: Vulnerability in Microsoft Publisher Could Allow Remote Code Execution (910729).
- Microsoft Security Bulletin MS08-012: Vulnerabilities in Microsoft Office Publisher Could Allow Remote Code Execution (947085).
- Microsoft Security Bulletin MS08-027: Vulnerability in Microsoft Publisher Could Allow Remote Code Execution (951208).
- Microsoft Security Bulletin MS09-030: Vulnerability in Microsoft Publisher Could Allow Remote Code Execution (969516).
- Microsoft Security Bulletin MS10-023: Vulnerabilities in Microsoft Office Publisher Could Allow Remote Code Execution (981160).
- Microsoft Security Bulletin MS10-036: Vulnerabilities in COM validation in Microsoft Office Could Allow Remote Code Execution (983235.
- Microsoft Security Bulletin MS10-056: Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (2269638).
- Microsoft Security Bulletin MS10-057: Vulnerability in Microsoft Office Excel Could Allow Remote Code Execution (2269707).
- Microsoft Security Bulletin MS10-079: Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (2293194).
- Microsoft Security Bulletin MS10-087: Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (2423930).
- Microsoft Security Bulletin MS10-105: Vulnerabilities in Microsoft Office Graphics Filters Could Allow for Remote Code Execution (968095).
- Microsoft Security Bulletin MS11-021: Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution (2489279).
- Microsoft Security Bulletin MS11-023: Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (2489293).
- Microsoft Security Bulletin MS11-045: Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution (2537146).
- Microsoft Security Bulletin MS11-072: Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution (2587505).
- Microsoft Security Bulletin MS11-072: Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution (2587505).
- Microsoft Security Bulletin MS11-072: Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution (2587505).
- Microsoft Security Bulletin MS11-096: Vulnerability in Microsoft Excel Could Allow Remote Code Execution (2640241).
- Microsoft Security Bulletin MS11-096: Vulnerability in Microsoft Excel Could Allow Remote Code Execution (2640241).
- Microsoft Security Bulletin MS11-096: Vulnerability in Microsoft Excel Could Allow Remote Code Execution (2640241).
- ASA-2006-189: Windows Security Updates for September 2006 - (MS06-052 - MS06-054)
- BID-19951: Microsoft Publisher Font Parsing Remote Code Execution Vulnerability
- CVE-2006-0001: Stack-based buffer overflow in Microsoft Publisher 2000 through 2003 allows user-assisted remote attackers to execute arbitrary code via a crafted PUB file, which causes an overflow when parsing fonts.
- SA21863: Microsoft Publisher Font Parsing Buffer Overflow Vulnerability
- SECTRACK ID: 1016825: Microsoft Publisher Buffer Overflow in Parsing `.pub` Files Lets Remote Users Execute Arbitrary Code
- US-CERT VU#406236: Microsoft Publisher does not adequately validate Publisher documents
- VUPEN/ADV-2006-3565: Microsoft Publisher pub File Handling Code Execution Vulnerability (MS06-054)
Platforms Affected:
- Microsoft Publisher 2000
- Microsoft Publisher 2002
- Microsoft Publisher 2003
Reported:
Sep 12, 2006
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net
* According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall IBM be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.