A subtle trend has been emerging over the last few years and it doesn’t appear to be abating: the number of insecure computer security products is growing. The very products designed to protect us are often the ones introducing the vulnerabilities.
These are products with weak configuration protection, easy-to-exploit denial-of-service attacks and easy security bypasses. I’m talking firewalls with old web server code and exploitable management interfaces; anti-virus products with buffer overflows; gateway products susceptible to DNS cache poisoning and in-line filtering software vulnerable to script injection.
Although most of the products I review are commercial products, open source products are just as vulnerable. For example, Ethereal, my favourite sniffer, seems to be caught in a beyond-ridiculous cycle of exploitable packet dissectors. It’s almost becoming the rare security software product that doesn’t end up having to be patched once or twice a year.
Even security appliances are taking a beating. Many are running an outdated Linux or BSD kernel, with no easy way to update. Some vendors will tell you updating the kernel will void the warranty. Almost all come with one or more undocumented listening ports that an intruder can probe.
Many security appliances don’t require secure VPNs between the management client and the server. I’ve seen many a vendor’s VPN tunnels that rely on HTTPS, SSL or SSH not work — even though it appeared to be doing so.
This is a travesty. Isn’t anyone testing these features before they ship? Shouldn’t security vendors ship their products with the latest patched stuff? Shouldn’t the products contain some sort of auto-update routine? Maybe the product shouldn’t automatically apply the patch, but there should be some sort of mechanism with which one can automatically search for and download the latest patches, then notify the administrator to apply them.
Customers want to believe that security product vendors are doing a better job at secure coding than nonsecurity product vendors. Certainly, it isn’t an abnormal expectation. The truth is that security vendor programmers are just as overworked as any programmers in any company. Oftentimes, like their counterparts, they haven’t received specific training in writing secure code or using secure coding practices.
While I was teaching advanced computer security classes at a very well known security vendor, one of their products was found to have a remotely exploitable buffer overflow affecting thousands of customers.
The vendor first learned about the exploit on a zero-day public mailing list. The guy in charge of researching the product and fixing the flaw was in my class. He had been waiting for years to take this particular class and refused to leave. What should have taken on a crisis-mode level of criticality and have been solved quickly took over a week to resolve, and I’m fairly confident that thorough regression testing was not involved.
Customers might have assumed that a moderate-sized team of programmers would be assigned to solve this problem and it would be priority number one. In reality, it was one guy, part-time, trying desperately to recreate and solve the problem using VMware on his laptop, all the while not letting a single class slide.
This isn’t a pretty story, but it’s probably not unique in the computer security field.
The problem of insecure computer security products is becoming so bad that malicious hackers are now targeting organisations with particular computer security products. If hackers can identify the defence tool, they can then sit back until the latest related exploit is announced and then use the public exploit code (which almost always follows the announcement these days) to compromise the organisation’s security defence. The hacker need only be quicker at using the exploit than the customer is at patching.
Personally, I’m getting fed up with the status quo. Here’s my open letter to computer security vendors with poor security practices:
To whom it may concern,
We are entrusting our enterprise security to your product. We expect our purchasing dollars to decrease our risk of malicious exploitation. As you are developing your super-duper product, take a step back and make sure secure coding is integrated into your products.
Make it easy for us to stay updated. Make sure your products don’t contain buffer overflows and dated programs, and include some form of auto-patching that customers can configure and manage. And, deliver products that are secure by default. In short, do your job.
I’m sure the company is staffed by lots of people I’d like to have a beer with and all of them are already overworked. But when your products become the most insecure piece of my environment and you don’t make it easy for me to stay on top of the security defence curve, I have a problem.
And I’ll let my IT dollars vote for my company’s security.
Grimes is a contributing editor at the InfoWorld Test Centre.