A. THE BUG/ISSUE (Varies from issue to issue)
[ol]- Summary - Give a clear summary in the topic subject, NOT here.
-
Can U reproduce the problem & if so how reliably?:
Yes, every time. -
If U can, exact steps to reproduce. If not, exactly what U did & what happened:
I downloaded a piece of malware, which devs will find attached to this post. (The malware name is spywar214). Then, after unzipping it, right-click on the executable and select the option to “Run in COMODO Sandbox”. Then, the malware will create window which envelops the entire screen. The only way to get out is to log off the computer or restart. You can start the task manager, but the FV screen quickly moves in front again before you can do anything. -
If not obvious, what U expected to happen:
An application running in the FV sandbox should not be able to force a window above the task manager. There should always be a way to access either the task manager or CIS in order to kill FV sandboxed processes. -
If a software compatibility problem have U tried the conflict FAQ?:
NA -
Any software except CIS/OS involved? If so - name, & exact version:
NA -
Any other information, eg your guess at the cause, how U tried to fix it etc:
Create an exception for the task manager to always be on top of FV sandboxed windows if manually invoked by the user. -
Always attach - Diagnostics file, Watch Activity process list, dump if freeze/crash. (If complex - CIS logs & config, screenshots, video, zipped program - not m’ware)
I have attached the diagnostics file (run after logging off and then logging back into the computer) and the KillSwitch process dump (run after logging off and then logging back into the computer).
[/ol]
B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
[ol]- Exact CIS version & configuration:
CIS version 6.2.285401.2860
Default Configuration
-
Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
Default Configuration
However, I had to disable the AV and the Cloud lookup so it wouldn’t automatically flag the file as dangerous and remove it. -
Have U made any other changes to the default config? (egs here.):
Default Configuration
However, I had to disable the AV and the Cloud lookup so it wouldn’t automatically flag the file as dangerous and remove it. -
Have U updated (without uninstall) from a CIS 5?:
No, this was a clean install.
[li]if so, have U tried a a clean reinstall - if not please do?:
NA
[/li]- Have U imported a config from a previous version of CIS:
No
[li]if so, have U tried a standard config - if not please do:
NA
[/li]- OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
Windows 7 x64 (fully updated), UAC disabled, Real System, run as administrator. -
Other security/s’box software a) currently installed b) installed since OS:
a) None b) None
[/ol]
[attachment deleted by admin]