QuarkXpress MSWord text-import extension buffer overflow
| quarkxpress-msword-textimport-bo (35369) |  High Risk |
Description:
QuarkXpress is vulnerable to a stack-based buffer overflow, caused by improper bounds checking by the MSWord text-import extension's (Word 6-2000 Filter.xnt) lstrcpy function. By persuading a victim to import a specially-crafted DOC file with an overly long font name, a remote attacker could overflow a buffer and execute arbitrary code on the system or cause the application to crash.
Platforms Affected:
- Microsoft, Windows Vista
- Quark and Quark Media House, QuarkXPress 7.2
Remedy:
No remedy available as of July 4, 2009.
Consequences:
Gain Access
References:
- QuarkXpress Web site, QuarkXPress - The industry-leading software for design and layout at http://www.quark.com/products/xpress/.
- vuln.sg Vulnerability Research Advisory 2007-07-11, QuarkXPress Word File Import Filter Buffer Overflow Vulnerability at http://vuln.sg/quarkxpress72-en.html.
- BID-24872: QuarkXPress Word Document Text-Import Font Handling Stack Buffer Overflow Vulnerability
- CVE-2007-3678: Stack-based buffer overflow in the MSWord text-import extension (Word 6-2000 Filter.xnt) in QuarkXPress 7.2 for Windows, when using the Rectangle Text Box tool for importing text, allows user-assisted remote attackers to execute arbitrary code via a long font name.
- SA25994: QuarkXPress Word Document Text-Import Font Handling Buffer Overflow
- SECTRACK ID: 1018385: QuarkXPress Stack Overflow in Word Import Filter Lets Remote Users Execute Arbitrary Code
- VUPEN/ADV-2007-2504: QuarkXPress MSWord Text-import Extension Client-Side Buffer Overflow Vulnerability
Reported:
Jul 11, 2007
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