Vulnerabilities / Threats

5/9/2017
11:15 AM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Microsoft Releases Emergency Patch For RCE Vuln

Flaw in Microsoft Malware Protection Engine called 'crazy bad' by researchers who discovered it.

Late last night Microsoft released an emergency out-of-band patch to fix a vulnerability in Microsoft Malware Protection Engine (MsMpEng) that one of the researchers who found it called "the worst Windows remote code exec(ution) in recent memory," and for which US-CERT released an alert.

Announced over the weekend by a pair of researchers working for the Google Project Zero team, Tavis Ormandy and Natalie Silanovich, the vulnerability allows attackers to carry out remote code execution (RCE) by feeding MsMpEng a simple malicious file to trigger memory corruption. According to Silanovich, the vulnerability only requires a simple exploit to leverage, requiring so little code that it can fit in a single tweet. According to Microsoft Security Advisory 4022344, the affected version of the engine must scan the specially crafted file, but that can be easily achieved a number of ways.

"For example, an attacker could use a website to deliver a specially crafted file to the victim's system that is scanned when the website is viewed by the user. An attacker could also deliver a specially crafted file via an email message or in an Instant Messenger message that is scanned when the file is opened," Microsoft advises. "In addition, an attacker could take advantage of websites that accept or host user-provided content, to upload a specially crafted file to a shared location that is scanned by the Malware Protection Engine running on the hosting server."

In fact, when Ormandy and Silanovich released their proof-of-concept code they warned anyone using Microsoft systems to take extra care with the file because simply downloading it could immediately crash MsMpEng in its default configuration. Given the triviality of exploit, the default-on status of MsMpEng in Windows systems from Windows 8 on up, and the permissions afforded to the service, Ormandy calls this particular hole "crazy bad."

"Vulnerabilities in MsMpEng are among the most severe possible in Windows, due to the privilege, accessibility, and ubiquity of the service," he wrote. "The core component of MsMpEng responsible for scanning and analysis is called mpengine. Mpengine is a vast and complex attack surface, comprising of handlers for dozens of esoteric archive formats, executable packers and cryptors, full system emulators and interpreters for various architectures and languages, and so on. All of this code is accessible to remote attackers."

Ormandy and Silanovich went through coordinated vulnerability disclosure procedures with Microsoft, which came up with this release within just a few days. Microsoft says that updates to the engine will be automatically installed with updated malware definitions for the affected products, such that the typical consumer end user should see the update applied within 48 hours. Consumers can speed up that timetable by manually updating their anti-malware software. Meanwhile, Microsoft advises enterprise customers to follow internal processes to confirm that their patch management software has approved and installed necessary definition and engine updates.

"Administrators of enterprise anti-malware deployments should ensure that their update management software is configured to automatically approve and distribute engine updates and new malware definitions. Enterprise administrators should also verify that the latest version of the Microsoft Malware Protection Engine and definition updates are being actively downloaded, approved and deployed in their environment," the advisory explains. 

The scramble to patch this vulnerability highlights the extreme sensitivity of flaws found within security products, say experts in the field. 

"The irony is that it is the product that is designed to protect these operating systems against malware which can now be targeted as a result of finding this issue," says Darron Gibbard, CTSO at Qualys. 

Steven Malone, director of security product management at email security company Mimecast agrees, explaining that the incident is also good lesson on why it's never good to depend on a single layer of security.

"Desktop security products often need high privileges in order to see everything and therefore any vulnerabilities can be particularly deadly," he says. "Incidents like this highlight that advanced security still requires a defense-in-depth strategy."

Related Content:

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.