Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Analytics

6/13/2007
01:20 AM
50%
50%

Trust Gets Buggy

Whether a flaw or a feature, Microsoft's attitude suggests bugs don't have to be fixed

This would be funny if it wasn't so sad. Microsoft has in the past three months declared that two security bugs are, in fact, features. The most recent involves IIS, the earlier one involves Word 2007. Apparently nobody at Microsoft realizes that the "It's not a bug, it's a feature!" should only be used as a punch line to a joke.

In the case of the Word bug, there is at least the consolation that Word is hardly an enterprise server application, as pointed out by Microsoft's David LeBlanc. In his analysis, crashing an application, in a way that you are "reasonably certain" it won't be exploitable, is a good thing. And he points out that you need to be absolutely certain you can safely return to code execution after catching an exception, and that triggering a crash may be the best way to do that.

Of course, in this case, the flaw is in the code that, um, loads a document. If the .docx parser, which is for a new file format, has so much code in it that wasn't designed for exception handling, it should be clear to even the most casual observer that there can be no reasonable expectation of a lack of exploitable bugs. This is really, really sad.

For IIS, we are in a different realm entirely. IIS is billed as an enterprise class Web server, suitable for all sorts of Web applications. The bug discovered finds the hit highlighting feature of IIS 5 relies only on ACL-based security, not on any sort of Web-server mechanisms (NTLM/basic authentication, IP restrictions).

The proposed solution? Upgrade to IIS 6 or better. Of course such an upgrade would likely involve an upgrade of server OS, testing of all Web server code on the new version, and a tremendous amount of pain and suffering for IT staff.

Naturally, a reasonable argument can be made that this work is inevitable, and that since IIS 6 has been out for several years now, it's about time to upgrade anyway.

The real problem here, however, isn't in the proposed solution. If Microsoft chooses to stop supporting IIS 5, that is within its rights. The problem is the attitude that a design flaw cannot, by definition, be a security bug.

Let's walk further down this same path. If I intentionally store passwords in plain text, or display a credit card number on the screen, or store users' Social Security numbers in cookies without asking first, then these are somehow not security flaws.

Hasn't Microsoft learned yet? For all the hype about Trustworthy Computing, the company sure don't seem like it understands much, or that the people providing the software have to be worthy of our trust.

— Nathan Spande has implemented security in medical systems during the dotcom boom and bust, and suffered through federal government security implementations. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Look Beyond the 'Big 5' in Cyberattacks
Robert Lemos, Contributing Writer,  11/25/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: We are really excited about our new two tone authentication system!
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-29440
PUBLISHED: 2020-11-30
Tesla Model X vehicles before 2020-11-23 do not perform certificate validation during an attempt to pair a new key fob with the body control module (BCM). This allows an attacker (who is inside a vehicle, or is otherwise able to send data over the CAN bus) to start and drive the vehicle with a spoof...
CVE-2020-29441
PUBLISHED: 2020-11-30
An issue was discovered in the Upload Widget in OutSystems Platform 10 before 10.0.1019.0. An unauthenticated attacker can upload arbitrary files. In some cases, this attack may consume the available database space (Denial of Service), corrupt legitimate data if files are being processed asynchronou...
CVE-2020-4127
PUBLISHED: 2020-11-30
HCL Domino is susceptible to a Login CSRF vulnerability. With a valid credential, an attacker could trick a user into accessing a system under another ID or use an intranet user's system to access internal systems from the internet. Fixes are available in HCL Domino versions 9.0.1 FP10 IF6, 10.0.1 F...
CVE-2020-11867
PUBLISHED: 2020-11-30
Audacity through 2.3.3 saves temporary files to /var/tmp/audacity-$USER by default. After Audacity creates the temporary directory, it sets its permissions to 755. Any user on the system can read and play the temporary audio .au files located there.
CVE-2020-16849
PUBLISHED: 2020-11-30
An issue was discovered on Canon MF237w 06.07 devices. An "Improper Handling of Length Parameter Inconsistency" issue in the IPv4/ICMPv4 component, when handling a packet sent by an unauthenticated network attacker, may expose Sensitive Information.