Microsoft Denies Fault in Hacks

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
According to Microsoft’s security response team, recent attacks that have compromised half a million Web sites are not due to any new or unknown flaws in Microsoft IIS or SQL Server.

In a blog posted late Friday night, Bill Sisk, of the Microsoft Security Response Center, wrote that the attacks are not due to any new or unknown security flaws in Internet Information Services or Microsoft SQL Server. Rather, he says, the attacks are made possible by SQL injection exploits, and he points Web developers to the company's list of best practices to prevent such attacks.
 
They are known exploits, therefore MS should have fixed them if they are aware of them...and I'm pretty sure the UN already utilized the methods they speak of to try and prevent such an attack..
 
It's a SQL injection problem, which is caused by bad application programming. What MS desribes in the link is actually true.
 
it's not due to any new or unknown flaws... if they're unknown, how do they know it's not the cause?
 
I'm pretty sure pxc is NOT talking out of his ass. So much blame goes to MS for bad application development. Thank you PXC for a voice of reason and logic.
 
It's a SQL injection problem, which is caused by bad application programming. What MS desribes in the link is actually true.
QFT

I actually work for an application security company (though I'm in a different division) - so besides the marketing, I can vouch for the technical veracity of such statements. The reality is that application programmers are frequently unaware that they create potential security risks in their applications due to the way they employ tools such as IIS and SQL. Hence, a market exists for products that examine the content of inbound HTTP queries and block SQL injection site-wide (and also products that scan HTTP responses and block leaked info).

Of course, M$FT could invest in developing or acquiring such a technology, and integrating it with IIS. However, for the time being they are satisfied to leave this as an opportunity for 3rd party vendors like my company - not that I'm complaining ;)

Basically, IIS makes it easy to set up a site - maybe too easy, since any n00b can do it. I could see an argument for making it easy (say, automatic) to validate inputs too - but then you're looking at the default mode of operation applying filters to everything, and that makes more work for the professional programmers who will want something other than the defaults. Changing a default always presents a huge upgrade challenge for the install base, which is the other side of this discussion. That's another reason it makes sense to apply that additional filtering outside IIS, as a 3rd party add-on.

However, the bottom line still comes back to coding practice - competent programmers always check their inputs. That includes validating fields in HTTP requests, inclusive of forms and cookies. The sad part is that once you develop a set of validation expressions for a platform, it is easy to make that a library and use it as a site standard, and use it on every input. I don't see how M$FT could be held responsible for a lack of professionalism among web developers.
 
Their lack of blame, responsibility, ownership whatever the heck you want to call it means nothing to someone like me who is getting attacked thousands of times a day ( http://www.patentlystupid.com/node/48113 ) by endless hordes of zombies. My only course of action to protect me from those zombies is to start blocking them at the firewall level using advanced filtering. All because all mighty MS is not to blame. A little guy like me on a shared hosting platform has to pay in bandwidth and cpu and memory resources andtime and irritation because they cant be bothered to make their software more secure and more difficult for an end user to setup with a wide open door. No instead I have to run scripts like fail2ban and spamassassin to protect my own back from your machines. You know GM got in trouble for making a truck that was easily damaged to the point it caused injury, you lack of ability to provide a secure product causes fiscal injury to those around you, however the little guys like us dont have the billions to hire lawyers to try to recoup our losses from you...

Thanks MS I am so glad to know its not 'your fault'.....

Is there any wonder why I quit being an MS MVP....
 
Basically, IIS makes it easy to set up a site - maybe too easy, since any n00b can do it. I could see an argument for making it easy (say, automatic) to validate inputs too - but then you're looking at the default mode of operation applying filters to everything, and that makes more work for the professional programmers who will want something other than the defaults. Changing a default always presents a huge upgrade challenge for the install base, which is the other side of this discussion. That's another reason it makes sense to apply that additional filtering outside IIS, as a 3rd party add-on.

Professional programmers should have no trouble adding one or two lines to old scripts to turn on compatability mode or change to whatever non-default setting they wany. If they're even half-way competent, they should be able to quite easily write a new script automating the changes to old scripts. It's the newbies we should be worrying about, not the professionals who are already competent in the art.
 
it's not due to any new or unknown flaws... if they're unknown, how do they know it's not the cause?

Because the cause it already known?

If I'm pouring water into bucket and it's pouring out the bottom through a whole, do I go to the water company and complain that some unknown issue is causing my bucket to leak?
 
Their lack of blame, responsibility, ownership whatever the heck you want to call it means nothing to someone like me who is getting attacked thousands of times a day
ASP.NET already can do URL parameter checking and stop execution when many types of "bad" parameters are passed (overflow and nasty characters used in SQL injection). That is similar to what many other web programming languages do for basic security.

It's not the only line of defense though, as any half-way competent web programmer knows. The problem is that not programmers are competent, or some simply make mistakes. I'm not sure what you're expecting MS to fix. Any more stringent changes will not magically fix legacy code that hasn't been touch in a long time and will not prevent the next exploit.
 
Back
Top