[Bug] SONAR quarantines VB6.exe while developing with Winsock

NIS 2010 version 18.7.2.3

 

Using the Visual Basic 6 component of Visual Studio 6, I was modifying an application that I wrote which uses the MS Winsock control to communicate via TCP. When I ran the program in the debugger (vb6.exe), SONAR immediately quarantined vb6.exe as soon as the command to send the TCP packet was executed. This packet was sent to a listener on the same machine (127.0.0.1) and in no way should've been considered suspicious.

 

I know I can "exclude the threat from future scans" but that excludes the action of sending TCP packets, not the quarantined executable wich I don't want to do

 

Note: I haven't updated to NIS 2012 yet because I have too many custom firewall rules and there is no way to export / import them

NIS 2010 version 18.7.2.3

 

Using the Visual Basic 6 component of Visual Studio 6, I was modifying an application that I wrote which uses the MS Winsock control to communicate via TCP. When I ran the program in the debugger (vb6.exe), SONAR immediately quarantined vb6.exe as soon as the command to send the TCP packet was executed. This packet was sent to a listener on the same machine (127.0.0.1) and in no way should've been considered suspicious.

 

I know I can "exclude the threat from future scans" but that excludes the action of sending TCP packets, not the quarantined executable wich I don't want to do

 

Note: I haven't updated to NIS 2012 yet because I have too many custom firewall rules and there is no way to export / import them