lnicula:
Can you please open a support Ticket and upload the code that is not detected?
I have.
lnicula:
It sounds like this one can be done with FTP signatures which is a lot easier than having to release code.
Gumblar is over 5 months old and that’s why I’m voicing my opinion publicly about eEyes failure to react. I know security exploits are almost out f control these days, but Old eEye would have been all over this one. "Don't take it as a diss, take it as an act of kindness, We wanna be in front while them fools is behind us" ~ Del
A proper solution might have been to:
#1 detect and block the upload of the code via FTP in modified html,htm,css,js,php and what ever else it infects.
#2 block outbound transmission of pages containing such code infected prior to FTP rules. Today Intelligent agents are still actively looking for exploited servers. Why? Image folders contain *.php files supplying anyone with IPs, FTP UIDs & PWDs used to infect the servers.
#3 detect the code in said files via file scanner offering to clean the infected code. Really its a simple find and replace.
More Info
In closing, Big companies are depending on your talent to protect them. They were sold this idea from marketing you were an active security company.I can't say it enough, your IPS has been your strength for along time in Blink & its been neglected. While I don’t trust any 1 “security” company, I know many who do and thats down right scaryif they rely on Blink alone. Really someone internal needs to bump some heads, get the trance flowing, and start the security party back-up! Trying to tackle that impossible feat security really is. Good luck to ya moving forward, & as always I will keep my EYE on you.