Classic ASP, SQL Security Audit

I would like someone to review Classic ASP (3.0) code and reveal specific weaknesses and exploits. Once identified, I'd like suggestions for closing these security holes. I'll provide various ASP scripts and in return would like: 1) A list of exploits 2) How those exploits may be tested (so that I can verify the weaknesses) 3) Suggestions on how to plug the holes. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Classic ASP 3.0 SQL Server 2000