Severity: Medium
30 April, 2007
Update:
On Thursday 26 April, we published an alert about a zero day vulnerability that affects Adobe Photoshop. By enticing one of your users into downloading a BMP, DIB, or RLE image file, and then opening it in Photoshop, an attacker can exploit this flaw to execute code on your user’s computer, with that user’s privileges. If your users have local administrator privileges, an attacker could use this flaw to gain complete control of their machines.
Over the weekend, the researcher who revealed the flaw above posted new exploit code for yet another unpatched Photoshop CS2 and CS3 vulnerability. This new flaw also stems from a buffer overflow vulnerability, except this time it involves PNG image files. If an attacker can trick your Photoshop users into downloading and opening a specially crafted PNG image, he can exploit this flaw to execute code and potentially gain complete control of your computer. Furthermore, this new Photoshop flaw also affects Photoshop Elements 5.0 and Corel Paint Shop Pro 11.20.
As he did with the earlier flaw, the researcher who discovered this vulnerability released exploit code for it without bothering to inform Adobe. They haven’t had time to release a patch for it yet. Until they do, we recommend you follow the tips found in the Solution section of our previous alert. Just add PNG files to your list of potentially malicious image types. As a convenient reference, we’ve duplicated the 26 April Photoshop alert, below. You can also find it in the LiveSecurity Latest Broadcasts archive.
Summary:
Yesterday, a gray hat researcher publicly released exploit code for a previously unknown buffer overflow vulnerability in Adobe Photoshop. By enticing one of your users into downloading an image file, and then opening it in Photoshop, an attacker can exploit this flaw to execute code on your user’s computer, with that user’s privileges. If your user has local administrative privileges, the attacker could gain total control of the victim’s PC. If any of your users run Photoshop, warn them of this flaw, and refer to the Solutions section of this alert for possible workarounds.
Exposure:
Adobe Photoshop is arguably the most popular image editing application used today. If you have a marketing department, or do any graphic design, chances are you have at least one computer running it.
In a post to a popular archive site, a gray hat researcher called Marsu released exploit code that attacks a zero day buffer overflow vulnerability in Adobe Photoshop CS2 and CS3. Specifically, the code creates a malicious BMP image file that, when opened in Photoshop, executes the Windows Calculator program. Opening your calculator may not sound dangerous. However, Marsu has written his exploit modularly, making it trivial for an attacker to replace his benign payload with a much worse one. In short, if an attacker can trick one of your users into downloading a malicious BMP, DIB, or RLE image file, and then opening that image in Photoshop, he could exploit this vulnerability to execute arbitrary code on your user’s computer, inheriting your user’s privileges. If your Photoshop users have administrative privileges, the attacker would gain complete control of their machines.
Since this vulnerability first came to our attention as a zero day exploit, without responsible disclosure, we don’t know everything about it yet. For example, Marsu wrote his exploit code specifically for Photoshop CS2 and CS3. However, we believe this flaw could potentially affect older versions of Photoshop, and other applications in the Photoshop family, such as the “lite” version of Photoshop bundled with scanners. Also, Marsu wrote his exploit to attack the French version of Windows XP SP2. We don’t know whether or not it affects the Mac versions. Despite these unknowns, one thing remains clear: Bad guys have access to an easily modifiable exploit that could give them full access to your Photoshop user’s computers. You should warn your Photoshop users of this flaw immediately.
Solution Path:
Since Marsu released his exploit without informing Adobe, they haven’t had time to patch. We will inform you when Adobe releases their patch. For now, follow the tips below to help protect yourself from this zero day attack:
- Inform your Photoshop users immediately. Tell your users that attackers can trigger this flaw using malicious BMP, DIB, and RLE images. Then your Photoshop users can avoid opening these sorts of images in Photoshop, especially when the images come from an untrusted source.
- Make sure Photoshop is not your default BMP image viewer. In Windows File Explorer, click Tools => Folder Options… => Files Types tab. Scroll through this list of file types looking for BMP, DIB, and RLE, then make sure that Photoshop is NOT the default application associated with these files. This may lessen the chance that your users accidentally open a malicious file in Photoshop.
- Use your Firebox to strip BMP, DIB, and RLE images. You can use your Firebox’s proxies to prevent your users from accessing these image files via the Web or email. However, this technique has drawbacks; see the next paragraph.
For All WatchGuard Users:
Some of WatchGuard’s Firebox models allow you to prevent your users from accessing BMP, DIB, and RLE image files via the Web or email (note that this method blocks all such files, both malicious and legitimate). If you like, you can temporarily mitigate the risk of this vulnerability by blocking these files using your Firebox’s HTTP and SMTP proxy services. However, many Web sites use BMP images heavily. Blocking them could significantly degrade your users’ Web browsing experience. If you still want to block these files, follow the links below for instructions:
- Firebox X Edge running 8.5
- Firebox III and X Core running WFS
- Firebox X Core and X Peak running Fireware Pro
- Vclass
- SMTP Proxy. You’ll have to create or adjust a custom proxy action based on SMTP-Incoming in order to strip .BMP, .DIB, and .RLE image files. If you have created your own Proxy Action based on SMTP-Incoming, you can edit it so that it blocks these files. In the Vcontroller software, click the Proxies button and double-click your custom proxy action. Under the Content Checking tab, change “Category” to Attachment Filename and click either the Add to Top or Insert After button (only one or the other will display). Next, type “BMP_files” as the new rule’s name, and choose Pattern Match. Next to Pattern Match, type “*.BMP” and select Strip as the Action. Repeat these steps for the other files extensions as well. Now you can apply this new Proxy Action to your SMTP rule to ensure your Firebox blocks these files.
- HTTP Proxy. You’ll have to create or adjust a custom proxy action based on HTTP-Outgoing in order to strip .BMP, .DIB, and .RLE image files. If you have created your own Proxy Action based on HTTP-Outgoing, you can edit it so that it blocks these files. In the Vcontroller software, click the Proxies button and double-click your custom proxy action. Under the Request General tab, change “Category” to URL Paths and click on Add. Next, type “BMP_files” as the new rule’s name, and choose Pattern Match. Next to Pattern Match, type “*.BMP” and select Strip as the Action. Repeat these steps for the other file extensions, too. Now you can apply this new Proxy Action to your HTTP proxy action to ensure your Firebox blocks these files.
Status:
Adobe hasn’t released a patch yet. We’ll inform you when they do.
Posted by bardissi
Posted by bardissi
Posted by bardissi