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.

Risk

3/26/2008
12:48 PM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

"New" Word Vulnerability: What Did Microsoft Know And When Did They Know It?

It turns out that Microsoft engineers knew about a vulnerability that could expose Word users to attacks, and knew about it for awhile before letting the rest of us in on the problem. A long while.

It turns out that Microsoft engineers knew about a vulnerability that could expose Word users to attacks, and knew about it for awhile before letting the rest of us in on the problem. A long while.The Jet Database Engine vulnerability exploitable via Word is one of those vulnerabilities that requires a targeted -- rather than broad -- attack.

Which doesn't mean it isn't a vulnerability, however "limited" (Microsoft's description) the risk it poses.

Nor was the risk so "limited" that Microsoft didn't feel obliged to let the world in on the problem after reports of some attacks began to circulate.

The vulnerability was announced by Microsoft last Friday -- two or three years after Microsoft became aware of it.

Take a look at this Microsoft security blog about the vulnerability -- and let me know if it annoys you that the company acknowledges awareness of this type of exploit and the vulnerability that invites it, yet did nothing about it. For three years.

My favorite part of the blog? The explanation that no alert -- much less fix -- for the problem was announced because Microsoft felt that an "attempt to attack customers using these issues was heavily mitigated" by file-blockers that prevented Outlook from opening the MDB files that could be exploited.

Mitigated!

So why let us know now?

To quote the blog again: "Everything changed with the discovery of this new attack vector..."

The new vector uses Word to open MDB files, unmitigating the mitigation, at least for users, as Microsoft puts it, of

Microsoft Word 2000 Service Pack 3, Microsoft Word 2002 Service Pack 3, Microsoft Word 2003 Service Pack 2, Microsoft Word 2003 Service Pack 3, Microsoft Word 2007, and Microsoft Word 2007 Service Pack 1 on Microsoft Windows 2000, Windows XP, or Windows Server 2003 Service Pack 1.

If you're running one of those you, to quote Microsoft again, "are vulnerable to these attacks."

Moving a step farther along the path from mitigated to unmitigated, there's this for all of you still running any of the vulnerable programs:

"Were investigating what it would take to release those fixes as part of the security update as a defense-in-depth change." I could tell Microsoft what it would take, and so could you, but that would require the use of unmitigated language that's not included in the bMighty stylesheet.

Fill in the blanks for me yourself -- and don't be mitigated about it.

Look: there are going to be big vulnerabilities and small vulnerabilities, holes that affect whatever the current largest market-share programs are, and holes hidden deep in older programs. We all know which ones get fanfare -- and which ones get fixed first.

But for the users running those older programs and thus exposed to the discovery of "new attack vectors" -- which are going to be discovered, no doubt of that -- the news that these holes have been waiting to be discovered for years, and that Microsoft knew it, is, well, it's just unmitigated ... [fill in this blank, too, according to your tastes and preferences in invective.]

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
'BootHole' Vulnerability Exposes Secure Boot Devices to Attack
Kelly Sheridan, Staff Editor, Dark Reading,  7/29/2020
Out-of-Date and Unsupported Cloud Workloads Continue as a Common Weakness
Robert Lemos, Contributing Writer,  7/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-14310
PUBLISHED: 2020-07-31
There is an issue on grub2 before version 2.06 at function read_section_as_string(). It expects a font name to be at max UINT32_MAX - 1 length in bytes but it doesn't verify it before proceed with buffer allocation to read the value from the font value. An attacker may leverage that by crafting a ma...
CVE-2020-14311
PUBLISHED: 2020-07-31
There is an issue with grub2 before version 2.06 while handling symlink on ext filesystems. A filesystem containing a symbolic link with an inode size of UINT32_MAX causes an arithmetic overflow leading to a zero-sized memory allocation with subsequent heap-based buffer overflow.
CVE-2020-5413
PUBLISHED: 2020-07-31
Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets" exploit when provided data contains mali...
CVE-2020-5414
PUBLISHED: 2020-07-31
VMware Tanzu Application Service for VMs (2.7.x versions prior to 2.7.19, 2.8.x versions prior to 2.8.13, and 2.9.x versions prior to 2.9.7) contains an App Autoscaler that logs the UAA admin password. This credential is redacted on VMware Tanzu Operations Manager; however, the unredacted logs are a...
CVE-2019-11286
PUBLISHED: 2020-07-31
VMware GemFire versions prior to 9.10.0, 9.9.1, 9.8.5, and 9.7.5, and VMware Tanzu GemFire for VMs versions prior to 1.11.0, 1.10.1, 1.9.2, and 1.8.2, contain a JMX service available to the network which does not properly restrict input. A remote authenticated malicious user may request against the ...