Author Topic: A case that the web shield doesn't work  (Read 4432 times)

0 Members and 1 Guest are viewing this topic.

F5

  • Guest
A case that the web shield doesn't work
« on: January 10, 2010, 11:30:23 PM »
There is a case that the web shield doesn't work well.

The web shield doesn't work when hxxp://www.timerental.jp/ is opened with Firefox 3.5.7, and Firefox tries to connect to the malware distribution site.
(The connection is blocked by my router. )
A standard shield works when the source code of the page is saved as a file, and detects it as JS:Illredir-C [Trj].
A similar phenomenon is confirmed also on infected other sites with JS:Illredir-C [Trj].

The connection is cut with the web shield in IE8.
Does anyone know a reason?

Log when IE8 is used
Warning : SYSTEM  1608  Sign of "JS:Illredir-C [Trj]" has been found in "hxxp://www.timerental.jp/" file.  

Log when Firefox is used
-- nothing

< environment >
Firefox 3.5.7
WinXP Pro SP3
IE8 (8.0.6001.18702)
avast4.8! Home (4.8.1368, VPS:100110-1, standard shield, network shield, web shield)
« Last Edit: January 10, 2010, 11:33:05 PM by F5 »

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: A case that the web shield doesn't work
« Reply #1 on: January 10, 2010, 11:54:32 PM »
Works fine for me using firefox 3.5.7 also on XP Pro SP3, I get the alert (see image1) and abort connection does just that (image2) firefox shows connection reset.

If you haven't got the following firefox add-ons I suggest you install them, NoScript and RequestPolicy. These security add-ons help prevent scripts being run and to cross site access .
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

F5

  • Guest
Re: A case that the web shield doesn't work
« Reply #2 on: January 11, 2010, 12:34:15 AM »
Hello DavidR.
Thank you for the reply.

Oops, If cache remains, it seems to become the above.
When I did view-source , it seems to have remained in the cache.
After I erased the cache, web shield works fine.

I did not know RequestPolicy.
I investigate it and want to add it to add-on.

Thank you.
« Last Edit: January 11, 2010, 12:45:10 AM by F5 »

Hermite15

  • Guest
Re: A case that the web shield doesn't work
« Reply #3 on: January 11, 2010, 12:39:51 AM »
works fine here too... ::)

F5

  • Guest
Re: A case that the web shield doesn't work
« Reply #4 on: January 11, 2010, 12:46:35 AM »
Hello Logos.

After I erased its cache, web shield works fine.

Thank you.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: A case that the web shield doesn't work
« Reply #5 on: January 11, 2010, 02:00:24 AM »
Oops, If cache remains, it seems to become the above.
When I did view-source , it seems to have remained in the cache.
After I erased the cache, web shield works fine.

Thank you.

You're welcome.

If you elect to view the source avast would (or should I would have thought) alert as that source would contain the malicious script data, but in a text format.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security