Re: Microsoft Security Advisory (912840): Vulnerability in Graphics Rendering Engine Could Allow Remote Code Execution

Re: Microsoft Security Advisory (912840): Vulnerability in Graphics Rendering Engine Could Allow Remote Code Execution

Secure Home | Search | About
 Microsoft Antivirus Discussions    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Re: Microsoft Security Advisory (912840): Vulnerability in Graphics Rendering Engine Could Allow Remote Code Execution David H. Lipman 12-29-2005
Posted by David H. Lipman on December 29, 2005, 2:21 pm
If you were  Registered and logged in, you could reply and use other advanced thread options

| X-post to Security, Security.Homeusers, IE6 & WinXP General newsgroups.
| Followup set to microsoft.public.security.
|
| Microsoft Security Advisory (912840): Vulnerability in Graphics
| Rendering Engine Could Allow Remote Code Execution
| http://www.microsoft.com/technet/security/advisory/912840.mspx
|
| Welcome to the Microsoft Security Response Center Blog!
| New Security Advisory for Possible Windows Vulnerability
| http://blogs.technet.com/msrc/archive/2005/12/29/416569.aspx

I received a a sample. the following is a report.

Note that Microsoft's AV solution ( is it really one ? ) doesn't recognize this
as a threat.

AntiVir 6.33.0.70 12.29.2005 TR/Dldr.WMF.Agent.D
Avast 4.6.695.0 12.29.2005 Win32:Exdown
AVG 718 12.29.2005 Downloader.Agent.13.AI
Avira 6.33.0.70 12.29.2005 TR/Dldr.WMF.Agent.D
BitDefender 7.2 12.29.2005 Exploit.Win32.WMF-PFV.C
CAT-QuickHeal 8.00 12.29.2005 WMF.Exploit
ClamAV devel-20051123 12.29.2005 Exploit.WMF.A
DrWeb 4.33 12.29.2005 Exploit.MS05-053
eTrust-Iris 7.1.194.0 12.29.2005 Win32/Worfo.C!Trojan
eTrust-Vet 12.4.1.0 12.29.2005 Win32/Worfo
Ewido 3.5 12.29.2005 Downloader.Agent.acd
Fortinet 2.54.0.0 12.29.2005 W32/WMF-exploit
F-Prot 3.16c 12.29.2005 security risk or a "backdoor" program
Ikarus 0.2.59.0 12.29.2005 Trojan-Downloader.Win32.Agent.ACD
Kaspersky 4.0.2.24 12.29.2005 Trojan-Downloader.Win32.Agent.acd
McAfee 4662 12.29.2005 Exploit-WMF
Microsoft ?? 12.29.2005 no virus found
NOD32v2 1.1343 12.28.2005 Win32/TrojanDownloader.Wmfex
Norman 5.70.10 12.29.2005 no virus found
Panda 9.0.0.4 12.28.2005 Exploit/Metafile
Sophos 4.01.0 12.29.2005 Troj/DownLdr-NK
Symantec 8.0 12.29.2005 Download.Trojan
TheHacker 5.9.1.064 12.28.2005 Exploit/WMF
Trend Micro 135 12.29.2005 TROJ_NASCENE.D
UNA 1.83 12.29.2005 no virus found
VBA32 3.10.5 12.28.2005 no virus found




--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm



Posted by on December 29, 2005, 2:45 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Data Execution Prevention?
What happened to DEP in XP SP2?

If this is a buffer overflow exploit, why then isn't DEP in XP SP2
shutting down the malicious code before it can run?

I would think that an image file would be marked as "data" in memory,
not as an executable image, although WMF might be different than say a
jpg or bmp, does anyone know for sure?

I keep my DEP setting on "Turn on DEP for all programs and services
except those I select"

http://www.microsoft.com/technet/security/prodtech/windowsxp/depcnfxp.mspx

"Microsoft Windows XP Service Pack 2 (SP2) helps protect your computer
against the insertion of malicious code into areas of computer memory
reserved for non-executable code by implementing a set of hardware and
software-enforced technologies called Data Execution Prevention (DEP).
Hardware-enforced DEP is a feature of certain processors that prevents
the execution of code in memory regions that are marked as data
storage. This feature is also known as No-Execute and Execution
Protection. Windows XP SP2 also includes software-enforced DEP that is
designed to reduce exploits of exception handling mechanisms in
Windows.

Unlike an antivirus program, hardware and software-enforced DEP
technologies are not designed to prevent harmful programs from being
installed on your computer. Instead, they monitor your installed
programs to help determine if they are using system memory safely. To
monitor your programs, hardware-enforced DEP tracks memory locations
declared as "non-executable". To help prevent malicious code, when
memory is declared "non-executable" and a program tries to execute code
from the memory, Windows will close that program. This occurs whether
the code is malicious or not."


Posted by PA Bear on December 29, 2005, 3:47 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
In fact, there are various recent posts elsewhere stating that DEP blocked
the exploit. YMMV.
--
~PA Bear

jacecarter@gmail.com wrote:
> Data Execution Prevention?
> What happened to DEP in XP SP2?
>
> If this is a buffer overflow exploit, why then isn't DEP in XP SP2
> shutting down the malicious code before it can run?
>
> I would think that an image file would be marked as "data" in memory,
> not as an executable image, although WMF might be different than say a
> jpg or bmp, does anyone know for sure?
>
> I keep my DEP setting on "Turn on DEP for all programs and services
> except those I select"
>
> http://www.microsoft.com/technet/security/prodtech/windowsxp/depcnfxp.mspx
>
> "Microsoft Windows XP Service Pack 2 (SP2) helps protect your computer
> against the insertion of malicious code into areas of computer memory
> reserved for non-executable code by implementing a set of hardware and
> software-enforced technologies called Data Execution Prevention (DEP).
> Hardware-enforced DEP is a feature of certain processors that prevents
> the execution of code in memory regions that are marked as data
> storage. This feature is also known as No-Execute and Execution
> Protection. Windows XP SP2 also includes software-enforced DEP that is
> designed to reduce exploits of exception handling mechanisms in
> Windows.
>
> Unlike an antivirus program, hardware and software-enforced DEP
> technologies are not designed to prevent harmful programs from being
> installed on your computer. Instead, they monitor your installed
> programs to help determine if they are using system memory safely. To
> monitor your programs, hardware-enforced DEP tracks memory locations
> declared as "non-executable". To help prevent malicious code, when
> memory is declared "non-executable" and a program tries to execute code
> from the memory, Windows will close that program. This occurs whether
> the code is malicious or not."


Posted by Tom [Pepper] Willett on December 29, 2005, 6:31 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
~Robear: Are you using DEP for ALL programs?

Tom
| In fact, there are various recent posts elsewhere stating that DEP blocked
| the exploit. YMMV.
| --
| ~PA Bear
|
| jacecarter@gmail.com wrote:
| > Data Execution Prevention?
| > What happened to DEP in XP SP2?
| >
| > If this is a buffer overflow exploit, why then isn't DEP in XP SP2
| > shutting down the malicious code before it can run?
| >
| > I would think that an image file would be marked as "data" in memory,
| > not as an executable image, although WMF might be different than say a
| > jpg or bmp, does anyone know for sure?
| >
| > I keep my DEP setting on "Turn on DEP for all programs and services
| > except those I select"
| >
| >
http://www.microsoft.com/technet/security/prodtech/windowsxp/depcnfxp.mspx
| >
| > "Microsoft Windows XP Service Pack 2 (SP2) helps protect your computer
| > against the insertion of malicious code into areas of computer memory
| > reserved for non-executable code by implementing a set of hardware and
| > software-enforced technologies called Data Execution Prevention (DEP).
| > Hardware-enforced DEP is a feature of certain processors that prevents
| > the execution of code in memory regions that are marked as data
| > storage. This feature is also known as No-Execute and Execution
| > Protection. Windows XP SP2 also includes software-enforced DEP that is
| > designed to reduce exploits of exception handling mechanisms in
| > Windows.
| >
| > Unlike an antivirus program, hardware and software-enforced DEP
| > technologies are not designed to prevent harmful programs from being
| > installed on your computer. Instead, they monitor your installed
| > programs to help determine if they are using system memory safely. To
| > monitor your programs, hardware-enforced DEP tracks memory locations
| > declared as "non-executable". To help prevent malicious code, when
| > memory is declared "non-executable" and a program tries to execute code
| > from the memory, Windows will close that program. This occurs whether
| > the code is malicious or not."
|



Posted by Matt Thompson on December 29, 2005, 8:52 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Hardware DEP computers will have DEP on for everything and the exploit will
be stopped.
Windows 2003 Server defaults for hardware or software DEP to be on for all
software, but can be changed.
Windows XP defaults to having DEP on just system services, which does not
protect against this threat.

McAfee VirusScan 8.0i and Entercept Buffer Overflow protection also stop
this threat.

> ~Robear: Are you using DEP for ALL programs?
>
> Tom
> | In fact, there are various recent posts elsewhere stating that DEP
> blocked
> | the exploit. YMMV.
> | --
> | ~PA Bear
> |
> | jacecarter@gmail.com wrote:
> | > Data Execution Prevention?
> | > What happened to DEP in XP SP2?
> | >
> | > If this is a buffer overflow exploit, why then isn't DEP in XP SP2
> | > shutting down the malicious code before it can run?
> | >
> | > I would think that an image file would be marked as "data" in memory,
> | > not as an executable image, although WMF might be different than say a
> | > jpg or bmp, does anyone know for sure?
> | >
> | > I keep my DEP setting on "Turn on DEP for all programs and services
> | > except those I select"
> | >
> | >
> http://www.microsoft.com/technet/security/prodtech/windowsxp/depcnfxp.mspx
> | >
> | > "Microsoft Windows XP Service Pack 2 (SP2) helps protect your computer
> | > against the insertion of malicious code into areas of computer memory
> | > reserved for non-executable code by implementing a set of hardware and
> | > software-enforced technologies called Data Execution Prevention (DEP).
> | > Hardware-enforced DEP is a feature of certain processors that prevents
> | > the execution of code in memory regions that are marked as data
> | > storage. This feature is also known as No-Execute and Execution
> | > Protection. Windows XP SP2 also includes software-enforced DEP that is
> | > designed to reduce exploits of exception handling mechanisms in
> | > Windows.
> | >
> | > Unlike an antivirus program, hardware and software-enforced DEP
> | > technologies are not designed to prevent harmful programs from being
> | > installed on your computer. Instead, they monitor your installed
> | > programs to help determine if they are using system memory safely. To
> | > monitor your programs, hardware-enforced DEP tracks memory locations
> | > declared as "non-executable". To help prevent malicious code, when
> | > memory is declared "non-executable" and a program tries to execute
> code
> | > from the memory, Windows will close that program. This occurs whether
> | > the code is malicious or not."
> |
>
>



Similar ThreadsPosted
Microsoft Security Bulletins for January January 9, 2007, 1:17 pm
Microsoft Security Centre and AV Identification June 6, 2007, 1:22 pm
published: Microsoft Security Intelligence Report October 25, 2006, 2:06 pm
RE: Microsoft Security Bulletins for February 2007 February 13, 2007, 8:27 pm
RE: Microsoft Security Bulletins for February 2007 February 13, 2007, 8:27 pm
Re: Microsoft Security Bulletins for February 2007 February 13, 2007, 8:33 pm
RE: Microsoft Security Bulletins for February 2007 February 13, 2007, 8:33 pm
Re: Microsoft Security Bulletins for June 2007 June 12, 2007, 8:13 pm
RE: Microsoft Security Bulletins for June 2007 June 15, 2007, 10:58 am
RE: Microsoft Security Bulletins for June 2007 August 14, 2007, 1:40 am

The site map in XML format XML site map

Contact Us | Privacy Policy