Yeah, but they gave standard big company BS about how it isn't an issue and everything's OK and we're always vigilant. Yeah, right. A developer probably woke up from his before-lunch nap early and gave one file a once-over to make sure there weren't any glaring bugs. Then he went to lunch, then came back for his after-lunch nap.At least WHMCS has looked at the exploit instead of ignoring it
Please, elaborate.Its an old one, but its real..its about a week or so old.
"The skid finds the exit; statement at the top of the udp.pl"Please, elaborate.
Anyway, I said this on LET:
So curtisg decided to run a PHP Analyzer (http://sourceforge.net/projects/rips-scanner/) on decoded WHMCS code, and he's posting all the false positives, including "exploits" generated by the analyzer that don't actually do anything.
Can he be more lame than this? Seriously, classic script kiddie stuff.
Curtisg, if you do infosec like you claim to, why can't you find actual vulnerabilities? Why not write an actual exploit, you know, by hand?
The difference between you and a skid that runs ./udp.pl is null. Well, actually, at least that skid may be successful
"The skid finds the exit; statement at the top of the udp.pl"
Anyways, what ever happened to his VPS panel that he was 90% done? If it was truly 90% done then he's a coding machine since he did so much in a matter of days. I know he came knocking on my door asking for Stallion 1's code to see if we were "both on the same page" on how to integrate parts.
I'm fairly sure he's also the guy that appeared on #frantech claiming he would cancel "all of his services" with us unless he was allowed to audit Stallion 2's code.
Francisco
Sure let me just zi- heeeeeyyyy waiiittttt a minuteCan I look at the code, please Francisco, ppppllll33333@@@@@555555553333333!!!!!!!!!!!!!
Oh boy, I better let him get a hold of that code right away, I'm going to be in pretty dire straits if I lose this one client.I'm fairly sure he's also the guy that appeared on #frantech claiming he would cancel "all of his services" with us unless he was allowed to audit Stallion 2's code.
I would have answered: "Thank you for your offer!"I'm fairly sure he's also the guy that appeared on #frantech claiming he would cancel "all of his services" with us unless he was allowed to audit Stallion 2's code.
I tend to reply to these with expediting their cancellations for them. Forcibly.I would have answered: "Thank you for your offer!"
I'm fairly sure he's also the guy that appeared on #frantech claiming he would cancel "all of his services" with us unless he was allowed to audit Stallion 2's code.
Someone needs to teach this kid what it's like to get punched in the face, that's all I'm saying. I'm not being unfair, I needed a good punch in the face at one point in my life. I got it too. Anyone in Canada? Obviously I'm joking, except about his need for a cold introduction to reality. If his desire was security it'd be one thing, but those of us who have been following his actions for some time will not question his motive: to cause chaos in an industry that "rejected" him (because he repeatedly scammed people) by any means necessary. When he uses up this method, he'll move on to a new one. The ability to hide behind other people's bad code and mask it as something "good" for the "community" is just an unintended side effect of his current methods.Please, elaborate.
Anyway, I said this on LET:
So curtisg decided to run a PHP Analyzer (http://sourceforge.net/projects/rips-scanner/) on decoded WHMCS code, and he's posting all the false positives, including "exploits" generated by the analyzer that don't actually do anything.
Can he be more lame than this? Seriously, classic script kiddie stuff.
Curtisg, if you do infosec like you claim to, why can't you find actual vulnerabilities? Why not write an actual exploit, you know, by hand?
The difference between you and a skid that runs ./udp.pl is null. Well, actually, at least that skid may be successful
Just read his posts, half of the vulnerabilities he found involve non-public-facing PHP files; how does that make any sense? The original XSS one was closest to an exploit, but it's ridiculous since single quotes are never used for attributes anywhere in WHMCS source code (and to work the exploit would need a user-supplied variable to be displayed within a singly-quoted HTML attribute).So it's nothing serious and already known to the WHCMS team?