error needs resolved

[cmunn]

i am getting the error below when i am going to www.sixberrylakeloj.com/admin before it comes up with the login screen. Anyone have any idea how to resolve this? I have Version 1.2.4 “Greenland” — March 29, 2008

thank you

Code: Select all

c1608e58b7a40647381b4667630bf061


Notice:  Undefined index:  p in /home/content/s/i/x/sixberry/html/admin/lang/update__af_ZA.nls.php on line 118

82d58bfc8dc7a2fa985939b01d5b694f
69175bee376c12eba6ddbd1f632a7f10


Notice: Constant PASSWD already defined in /home/content/s/i/x/sixberry/html/admin/lang/new__af_ZA.nls.php on line 106

Fatal error: Cannot redeclare say() (previously declared in /home/content/s/i/x/sixberry/html/admin/lang/update__af_ZA.nls.php:108) in /home/content/s/i/x/sixberry/html/admin/lang/new__af_ZA.nls.php on line 108

[cmunn]

bump please help. i was able to delete files that were created on may 20th. then i was installing intrusion module and it gave me a error half way into the installation. now the login doesnt have a gui interface.

[calguy1000]

this error has been encountered twice today on the IRC channel, and thanks to somebody with some patience, and the ability to explain a few things when asked, we were able to (somewhat) isolate the problem.  Here is the recommended action:

1) Delete all of your files, including the database from your host
2) restore from backup that is confirmed good
3) Upgrade to CMS 1.2.5 ASAP

It appears that somebody is doing a distributed attack and looking for sites that haven't upgraded to CMS 1.2.5 yet.

So if you haven't upgraded to CMS 1.2.5 yet, here is your warning.

[Pierre M.]

It appears that somebody is doing a distributed attack and looking for sites that haven't upgraded to CMS 1.2.5 yet.

Woah ! Big success ! CMSms seems to be spread as much as some famous OS

[biliousfrog]

OK...I've got the same problem

Is there a way to sort this without deleting the database?...or find a way of knowing when this exploit was implemented?

I can get a database restore from my host but without knowing when this was implemented I don't know when I need to restore  from...sounds dumb I know! I will make regular backups now but I didn't see a point before now.

[calguy1000]

check your error logs for strings like "postlet", etc.  from my knowledge it was the vulnerability that was fixed in v 1.2.5 that peopel are taking advantage of.