Alerte cheval de troie (OpenX)

I will find a solution for an upgrade as soon as possible :stuck_out_tongue:

Can you please tell me how you find the malicious script that was injected in the database ? (your answer will help me for the futur)

Regards,

Frederic

I have no idea, I was never on that side of the problem 8)

You can simply look at it in something like mysqladmin (if the SQL DB is mysql)
Or you can make text dump and then try to grep.
Or write some sql command using on append and prepend columns.

Can you please tell me how you find the malicious script that was injected in the database ? (the “+"")[$a],__$:++$a,$$:(!+"")[$a],$:++$a,$_$$” )

Thank you,

It’s our know-how as antivirus company to decide if some script is bad or not. We simply found strange redirection by some heuristic in avast, downloaded the samples, checked what they do, and decided to detect it. There is no general answer to such question, I’m afraid.

ok, thank you for you great help … !

I renamed the title of the thread “Fause alerte cheval de troie (OpenX)” → “Alerte cheval de troie (OpenX)” :wink:

Frederic

It must be noted, that simply upgrading to revive 3.0.2 is NOT ENOUGH!!!
If your database has been sql-injected, you must clean it also:

  1. stop the ad-server
  2. remove all the files under /var/cache
  3. The affected tables in mysql are named ‘audit’ and ‘zones’ (plus prefixes in front if you use them)
  4. Open the admin panel and for each of the zones:
    4.1. Click on the ‘Advanced’ tab and remove the malicious script from the prepend/append fields, then save the changes
    4.2. For each of the zones, there would be a record in the ‘audit’ table cotaining the script in the ‘details’ field. Delete these records and you are fine - Avast should stop complaining anymore.

Problem solved
URL was unblocked

Thanks Kubecj.