Nod32 Firewall fails in Tests

Discussion in 'ESET Smart Security v3 Beta Forum' started by timark6, Sep 22, 2007.

Thread Status:
Not open for further replies.
  1. timark6

    timark6 Registered Member

    Sep 22, 2007
    I recently found a forum where someone tested nod32 firewall in nod32 smart security 3.0 and it failed most of the tests. So it has to improve a lot.

    Here is the copy of the results.

    Firewall Tests

    I) GRC Shields UP!

    - Port Test:

    "Your system has achieved a perfect "TruStealth" rating. Not a single packet — solicited or otherwise — was received from your system as a result of our security probing tests."

    - Messenger Spam:

    No spam was received

    II) Firewall Leak Tester

    1. LeakTest:

    Passed! When Leak Tester attempted to connect, Eset firewall presented a neat prompt asking me whether to allow it to connect it or not.

    2. TooLeaky:

    Passed! There was no leak.

    3. FireHole:

    The AntiVirus module picked this up as a trojan and didn't allow to download. Since I couldn't disable the antivirus, I had to remove "EXE" from the file-types to be scanned.

    Failed! FireHole was able to connect by injecting code into the Internet Explorer process, since IE was allowed to connect normally, ESS didn't prompt or alert. This however, shouldn't be a problem if you're on Vista.

    4. Yalta:

    Can't Say - ESS did give a allow/deny prompt , but it was too late - Yalta had already sent UDP packets. However, when "Deny" was clicked, a new rule was created and Yalta was unable to send any further packets.

    5. Outbound:

    Did Not run - Outbound was unable to detect the ethernet adapter, and hence was unable to work.

    6. PCAudit:


    7. AWFT:

    Test 1 - Failed!*
    Test 2 - Failed!*
    Test 3 - Failed!**
    Test 4 - Failed!*
    Test 5 - Failed!
    Test 6 - Failed!

    Note: All above tests failed on Windows XP but passed on Windows Vista.

    8. Thermite:


    9. CopyCat:


    10. MBTest:

    Did not run. Apparently the MAC has to be hardcoded, but the source files aren't available for download.

    11. WallBreaker:

    Test 1 : Failed!*
    Test 2 : Failed!*
    Test 3 : Failed!*
    Test 4 : Failed!*

    12. pcAudit


    13. Ghost


    14. DNStester

    15. Surfer


    16. Breakout

    Did not run. File not found.

    Summary of areas where ESS fails

    - DLL Injection / Process patching
    - Launching under different context
    - Timed attacks / PID Changing
    - DDE based attacks

    For full review visit
  2. Nelu

    Nelu Registered Member

    Apr 6, 2007
    this test was made on april 2007 with an another version of NOD32 BETA
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.