|
BugTraq
what is this? Jan 13 2008 04:01PM crazy frog crazy frog (i m crazy frog gmail com) (5 replies) Re: what is this? Jan 15 2008 05:16AM Denis (sp23 internode on net) (3 replies) Re: what is this? Jan 15 2008 06:12AM crazy frog crazy frog (i m crazy frog gmail com) (2 replies) Re: [Full-disclosure] what is this? Jan 15 2008 06:45AM Nick FitzGerald (nick virus-l demon co uk) (1 replies) Re: [Full-disclosure] what is this? Jan 15 2008 08:26AM crazy frog crazy frog (i m crazy frog gmail com) (1 replies) Re: [Full-disclosure] what is this? Jan 15 2008 05:22PM Gadi Evron (ge linuxbox org) (1 replies) Re: [Full-disclosure] what is this? Jan 15 2008 05:24PM crazy frog crazy frog (i m crazy frog gmail com) Re: [Full-disclosure] what is this? Jan 14 2008 09:34AM 3APA3A (3APA3A SECURITY NNOV RU) (1 replies) |
|
Privacy Statement |
> Dear crazy frog crazy frog,
>
> Clear your computer from trojan, change FTP password for you site
> hosting access, because it's stolen, access your hosting account via
> FTP and remove additional text (usually at the end of the file, after
> </html>) from all HTML/PHP pages.
Ummmm -- the only part of that likely to be relevant here is the last.
These kinds of web page "compromises" are typically achieved through
bad/ill-configured/non-updated server-side web applications (or their
underlying script engines) and are typically achieved without requiring
any more special or privileged access to the victim sites than the
ability to run a clever Google search or your own brute-force spidering
via a bot-net, etc.
Of course, simply removing the undesired iframe/script/etc tags from
your compromised pages is not enough. Although doing so does not mean
that this attacker will come back, it equally does nothing to close the
hole they used in the first place, and the next attacker searching for
that hole will hit you just as easily and indiscriminately...
Regards,
Nick FitzGerald
[ reply ]