You keep referring to this as an exploit, when in fact, it isn't. David explained earlier that it is a common fact that scripts can be repeatedly run no matter what kind of checking Infopop were to put in UBB.

The admin logging idea is fine and dandy, but wouldn't do anything to keep someone from executing the script hundreds of times in an attempt to bring your server to its knees.

Quote
Originally posted by David Dreezer
Last time - the truth is that if it can be reached from the internet it can be operated repeatedly. There is no escaping that. No amount of floodchecking is going to fix it either. Floodcheck still requires perl to startup, compile the scripts, run it's checks against a flat file that it has to open, and then exit. Same answer as a refer check in making the avatar window a POST. No real savings.
So see, even floodchecking or admin logging would still require the above to activate, in turn, causing the load you are asking them to try to prevent by the script performing as designed. Admin loging of requests might actually amplify the problem by introducing more load into the mix by doing additional file i/o.

The whole issue centers around the fact that for UBB to do anything to stop the excessive requests, perl must be started, and the script complied. There is where your server was getting the snot kicked out of it. All of the Perl requests. You can do the same thing with just about any other message board out there. Send enough requests to it, and of course the server will take a beating.

The only way any kind of governor would be effective is on the server, otherwise you get back to the Perl.

---------------------
Suite Madame Blue....Gaze in your looking glass..you're not a child any more!
TheGeeksInc.com Forums
Have you tried Everwars yet?