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
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Exploits Released for As-Yet Unpatched Critical Citrix Flaw
Jai Vijayan, Contributing Writer,  1/13/2020
Microsoft to Officially End Support for Windows 7, Server 2008
Kelly Sheridan, Staff Editor, Dark Reading,  1/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7227
PUBLISHED: 2020-01-18
Westermo MRD-315 1.7.3 and 1.7.4 devices have an information disclosure vulnerability that allows an authenticated remote attacker to retrieve the source code of different functions of the web application via requests that lack certain mandatory parameters. This affects ifaces-diag.asp, system.asp, ...
CVE-2019-15625
PUBLISHED: 2020-01-18
A memory usage vulnerability exists in Trend Micro Password Manager 3.8 that could allow an attacker with access and permissions to the victim's memory processes to extract sensitive information.
CVE-2019-19696
PUBLISHED: 2020-01-18
A RootCA vulnerability found in Trend Micro Password Manager for Windows and macOS exists where the localhost.key of RootCA.crt might be improperly accessed by an unauthorized party and could be used to create malicious self-signed SSL certificates, allowing an attacker to misdirect a user to phishi...
CVE-2019-19697
PUBLISHED: 2020-01-18
An arbitrary code execution vulnerability exists in the Trend Micro Security 2019 (v15) consumer family of products which could allow an attacker to gain elevated privileges and tamper with protected services by disabling or otherwise preventing them to start. An attacker must already have administr...
CVE-2019-20357
PUBLISHED: 2020-01-18
A Persistent Arbitrary Code Execution vulnerability exists in the Trend Micro Security 2020 (v160 and 2019 (v15) consumer familiy of products which could potentially allow an attacker the ability to create a malicious program to escalate privileges and attain persistence on a vulnerable system.