Separate names with a comma.
Discussion in 'General' started by Nokki, Jun 13, 2010.
That doesn't seem like a terribly sophisticated script.
It would be rather strange & disappointing if it does indeed let someone suck up a permissions restricted file off a LSWS server, and perhaps set up the attacker to do even more.
Perhaps this is an old bug that was fixed and only affects those that haven't upgraded?
I've tested this on 4.0.13 and 4.0.14 on x86 and x64 and it's not working.
There's another version floating about which does work.
This needs patching immediately. If the mods want the link to the other version, PM me.
I can confirm that it does work on 4.0.14. A mod_security rule appears to sufficiently block the attempts at this time.
What rule are you using? There are two versions of this exploit and the rule in the WHT thread only works for one.
The one on WHT.
Do you have a rule for this other exploit? Or maybe you can PM me the link to it and I can see if we can get one working.
I've also now verified that this is indeed a legitimate vulnerability and exploit.
I'm interested too, just enabled mod_security first time ever ;-)
Due to monthly cost - or yearly I'm shocked this hasn't been patched up yet or announced by LiteSpeed, though I do understand it's weekend should someone give then a ring a ding?
I just had an email from George saying it's being looked in to and they'll post a fix later today if they're able to replicate it.
Now I like to hear that
Uh oh. So, there's only one mod_security rule?
Are there any serious bugs in 4.0.14? It still haven't been activated in the auto upgrader in the web console.
It also affects 4.0.11,12 and 13 so it's not just a .14 thing.
I've not had a single issue that I can point out that is with 4.0.14, I used 4.0.13 for a few days or so when we fire'd up LiteSpeed on our cpanel box may 29th and back around Feb, .14 just seemed better
please try to test latest build
4.0.15 for linux version has been built and ready for download.
please help test to confirm the issue is resolved. just go to download page and replace 4.0.14 with 4.0.15 in url.
Thanks for the quick fix.
Installed and tested and it seems to work perfectly, no longer an issue
All platform builds have been updated.
If you are unable to upgrade at this moment, please add mod_security rules to block this exploit suggested by khunj on webhostingtalk
4.1RC build will be updated later.
Upgraded all servers and it seems to resolve the issue. Though the web console now seems to think 4.0.13 is the latest and should be installed.
Same. I've gotten dozens of notifications to upgrade to .13.