Vulnerability Note VU#625856
Microsoft Windows LoadImage API vulnerable to integer overflow
Overview
The Microsoft Windows LoadImage API routine is vulnerable to an integer overflow that may allow a remote attacker to execute arbitrary code on a vulnerable system.
Description
The LoadImage API routine is used to load an image from a file on Microsoft Windows platforms. The LoadImage API is included part of the USER 32 library. A lack of input validation on user supplied input to the LoadImage API routine may allow an integer overflow to occur. If a remote attacker supplies a specially crafted image file to a vulnerable system, that attacker may be able to trigger the integer overflow to compromise that system. According to public reports, many Microsoft Windows are affected. However, reports also indicate Windows XP with Service Pack 2 is not vulnerable, but we have not confirmed this. |
Impact
If a remote attacker can persuade a user to access a specially crafted image file, the attacker may be able to execute arbitrary code on that user's system, possibly with elevated privileges. Potentially any operation that displays an image could trigger exploitation; for instance, browsing the file system, reading HTML email, or browsing websites. |
Solution
Apply Patch
|
Systems Affected (Learn More)
| Vendor | Status | Date Notified | Date Updated |
|---|---|---|---|
| Microsoft Corporation | Unknown | 06 Jan 2005 | 11 Jan 2005 |
CVSS Metrics (Learn More)
| Group | Score | Vector |
|---|---|---|
| Base | N/A | N/A |
| Temporal | N/A | N/A |
| Environmental | N/A | N/A |
References
- http://www.securityfocus.com/archive/1/385342
- http://www.xfocus.net/flashsky/icoExp/index.html
- http://secunia.com/advisories/13645/
- http://www.microsoft.com/technet/security/bulletin/ms05-002.mspx
Credit
This vulnerability was reported by flashsky fangxing and eEye Digital Security.
This document was written by Jeff Gennari.
Other Information
- CVE IDs: CAN-2004-1049
- Date Public: 23 Dec 2004
- Date First Published: 06 Jan 2005
- Date Last Updated: 12 Jan 2005
- Severity Metric: 44.75
- Document Revision: 50
Feedback
If you have feedback, comments, or additional information about this vulnerability, please send us email.