Our webserver got hit last night with a SQL injection attack. I have to admire the elegance of the code, it's really ingenious, a buffer overrun exploit that translates into an MSSQL cursor update statement. Slick. Want the details?
Ours was one of thousands of web providers that were hit in the last week or so. We recovered from it in a matter of a few minutes: restored the database, added a quick bandaid to limit this sort of thing in the future. Over the next week or so, I'll do an audit of my code and take what measures I can. I deliberately wrote my code to prevent this, but I didn't anticipate something like this, obviously.
( Courtesy snip... )
Ours was one of thousands of web providers that were hit in the last week or so. We recovered from it in a matter of a few minutes: restored the database, added a quick bandaid to limit this sort of thing in the future. Over the next week or so, I'll do an audit of my code and take what measures I can. I deliberately wrote my code to prevent this, but I didn't anticipate something like this, obviously.
( Courtesy snip... )