Vulnerabilities / Threats

2/5/2010
04:17 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Microsoft Patch To Leave IE Hole Open

The company plans to release 13 security bulletins next week, but the Internet Explorer vulnerability identified on Wednesday won't be among them.

Microsoft on Thursday said that its monthly security patch, to be issued on Tuesday, February 9th, will include 13 security bulletins.

That's the largest number of security bulletins issued in February for the past four years, according to Sheldon Malm, senior director of security strategy at Rapid7.

Next week's patch is scheduled to include five "critical" bulletins. Two of the bulletins affect Microsoft Office, and eleven affect Microsoft Windows.

Malm notes that all of Microsoft's operating systems, including Vista and Windows 7, will get fixes. "I won't be surprised if Microsoft is playing catch-up on some lingering vulnerabilities from last year," he said in an e-mailed statement.

One vulnerability that won't be fixed this month can be found in Internet Explorer. Microsoft on Wednesday issued a security advisory, stating that it is investigating a publicly reported vulnerability in versions of its Web browser.

"Our investigation so far has shown that if a user is using a version of Internet Explorer that is not running in Protected Mode an attacker may be able to access files with an already known filename and location," Microsoft's advisory says.

Core Security says that in order to exploit the Internet Explorer vulnerability, an attacker would only have to entice a user to click on a URL or visit a malicious Web site, without any other interaction. A successful attacker would gain the ability to read files on the user's system but couldn't run arbitrary code without restrictions.

Microsoft lists a number of mitigating factors which could limit attempts to exploit this vulnerability.

Last month, Microsoft issued an emergency, or out-of-band, security patch for Internet Explorer. The patch addressed a vulnerability said to have been used in a cyber attack from China on Google and a number of other companies.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
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
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.