Aldryic C'boas
The Pony
Regardless of original intentions, I highly doubt they'll attempt to contact the guy again, now knowing that any correspondence won't be taken seriously.
(coughs)
You don't reach out to one single guy for an audit of a software as expansive and non-exhaustive as WHMCS, if you're serious about said audit. Granted the guy is causing you grief, but a single guy against a (possible) team of security professionals won't work.Because the tin-foil-hat donning people in this arena react just as you did.
If they can pay that single guy any amount of money to sign an NDA, even if he doesn't find any exploits during that time it's still worth the money for them. Their goal is most likely preventing public disclosure more than obtaining an actual audit since, like you said, they would better off going to a reputable team.You don't reach out to one single guy for an audit of a software as expansive and non-exhaustive as WHMCS, if you're serious about said audit. Granted the guy is causing you grief, but a single guy against a (possible) team of security professionals won't work.
?(coughs)
X-Originating-IP: 91.138.253.244
TOR - Hol.gr
Seems like they just fixed a few bugs that were reported / discovered. (Doesn't PHP processor already take care of HTTP split attacks?) A real positive move would be to get rid of register globals and replace their custom SQL processing with PDO stored procedures.Either way, this was WHMCS's first positive move in restoring some faith in them.
They fixed multiple bugs/exploits that their team and a software auditor found. This means that somebody else is looking at the code at least which is a step in the right direction.Seems like they just fixed a few bugs that were reported / discovered. (Doesn't PHP processor already take care of HTTP split attacks?) A real positive move would be to get rid of register globals and replace their custom SQL processing with PDO stored procedures.
You'd think that being part of cpanel they would have a preferred team. Honest question, when was the last time cPanel had a 0 day exploit?They fixed multiple bugs/exploits that their team and a software auditor found. This means that somebody else is looking at the code at least which is a step in the right direction.
Personally, this is the last one I can find regarding cPanel 0day: http://www.exploit-db.com/wp-content/themes/exploit/docs/14864.pdfYou'd think that being part of cpanel they would have a preferred team. Honest question, when was the last time cPanel had a 0 day exploit?
I've seen some XSS stuff but nothing granting root in ages.
Francisco
Christ don't give them any ideas about rewriting WHMCS into PERL.Personally, this is the last one I can find regarding cPanel 0day: http://www.exploit-db.com/wp-content/themes/exploit/docs/14864.pdf
So what you're saying is, they have an indefinite amount of time?WHMCS has until November 31st to restore my confidence
This year of course. That's when 5.1.x is EOL and I'm not confident enough to upgrade to 5.2.x with the recent craziness.So what you're saying is, they have an indefinite amount of time?
Semantics aside; this mess is getting a bit old. Both the kid dicking them around and WHMCS themselves for expecting us to believe that a couple of incremental patches will fix poor coding. Realistically, you can expect the same poor coding practices throughout the entire platform - leaving it to just be a matter of time before very similar exploits are found. I wouldn't count on confidence unless they suddenly announce that not only have they brought in a new group of experienced coders, but the next release would be WHMCS 6 rather than these silly band-aid patches.
WHMCS has until November 31st to restore my confidence.
So what you're saying is, they have an indefinite amount of time?
I think what Aldryic want's to say here is that November only has 30 daysThis year of course.