Author Topic: What a webmaster can do to avoid reinfection...update, patch etc.  (Read 1702 times)

0 Members and 1 Guest are viewing this topic.

Offline polonus

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 33900
  • malware fighter
Hi folks,

Sometimes we check sites against malware infections. Later we find the malware has been taken down,
still the website software, like Wordpress for instance, has not been updated or has not been fully updated for all of the webpage. This makes a re-infection possible. Then we see that the website server transmits the full serversoftware version number. This should be avoided, because it is making it easy for hackers to know what exploits would work against it. A website could also give away that it generates dynamic webcontent, also an additional risk,

polonus
Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76037
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: What a webmaster can do to avoid reinfection...update, patch etc.
« Reply #1 on: January 15, 2012, 07:25:55 AM »
Later we find the malware has been taken down, still the website software, like Wordpress for instance, has not been updated or has not been fully updated for all of the webpage. This makes a re-infection possible.

Not only possible, but very likely.
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline polonus

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 33900
  • malware fighter
Re: What a webmaster can do to avoid reinfection...update, patch etc.
« Reply #2 on: January 15, 2012, 09:14:25 PM »
Hi Asyn,

For instance like this with Apache:
By default Apache configuration file has the following entries.

===
ServerTokens ProductOnly
ServerSignature On
===

Change the above lines to the following.

===
ServerSignature Off
ServerTokens Prod
===
restart and you are done.
Now the wannabee hacker has to actively probe to get a near guess at what they are/were looking for and can get logged. As they are always going for the low hanging fruit, they will probably pass your door, especially when they use automatic crawling to avoid detection. The malversant also can do a sitecheck but not with the best of intentions at heart.
Javascript, Java applets, Silverlight, Flash can also add to security risks as can be the use
of hidden iFrames, certain type of tracking code then may have been maliciously altered. Check also for script injections, obfuscation you are not familiar with, code outside HTML that should not be there, etc. etc.

polonus
Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!