Forum Thread: comdlg32 ActiveX Control 6.x

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
Programs

See the original Secunia vulnerability report for:
comdlg32 ActiveX Control 6.x

Relating to this vendor:
Microsoft
And, this specific program:
comdlg32 ActiveX Control 6.x

Secunia comdlg32 ActiveX Control 6.x
Secunia Official 21st Aug, 2012 04:49
Ranking: 0
Posts: 0
User Since: -
System Score: -
Location: Copenhagen, DK
Vulnerability report: comdlg32 ActiveX Control 6.x

jackelerwon RE: comdlg32 ActiveX Control 6.x
Member 21st Aug, 2012 04:49
Score: 0
Posts: 1
User Since: 21st Aug 2012
System Score: N/A
Location: US
Last edited on 21st Aug, 2012 04:49
I see no threads about comdlg32 Active Control 6x

I have this on my pc, It comes to me from the torque game engine instalation.
The only problem i see is ,that the installer makes a zombie install to the program files/torque folder, and acually puts the file in the system32 folder. Every time i start the game engine to work on my game, the engine trys to acces the internet, I have it blocked in my firewall. I dont see this as a threat ,I trust garage games as a respectull company. but since i found this install i will post a thread in the T3d private forums to find out all i can about the activex controler.

If anyone in here can enlighten as to what the file acually does it would be most apreciated.

Thank you
Thomas
Was this reply relevant?
+0
-0
ddmarshall RE: comdlg32 ActiveX Control 6.x
Dedicated Contributor 21st Aug, 2012 10:24
Score: 1232
Posts: 978
User Since: 8th Nov 2008
System Score: 98%
Location: UK
Comdlg32.ocx (Common Dialogs) is part of the Visual Basic 6.0 Runtime - see http://msdn.microsoft.com/en-us/vstudio/ms788708

Not to be confused with comdlg32.dll which is included in Windows.

The Visual Basic Runtime needs to be updated to resolve an issue with Common Controls (comctl32.ocx). You cannot do this yourself. The application needs to be reissued by the developer with the updated runtime.
http://www.microsoft.com/en-us/download/details.as...

According to Microsoft SRD, you can use EMET to protect the application until a fix is available from the developer.
http://blogs.technet.com/b/srd/archive/2012/08/14/...

--
This answer is provided “as-is.” You bear the risk of using it.
Was this reply relevant?
+0
-0