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.

Threat Intelligence

12/20/2018
05:05 PM
50%
50%

Attackers Use Scripting Flaw in Internet Explorer, Forcing Microsoft Patch

Microsoft issues an emergency update to its IE browser after researchers notified the company that a scripting engine flaw is being used to compromised systems.

Microsoft issued an emergency patch Wednesday after security researchers warned that attackers were using a vulnerability in Internet Explorer's scripting engine to compromise computers.

The vulnerability, designated CVE-2018-8653, affects the scripting engine in Microsoft's Internet Explorer when it executes Visual Basic scripts (VBScript) and Microsoft's version of Javascript. Attackers that convince a user to view a specially constructed Web page, HTML document, PDF file, or Office document can execute malicious programs due to a memory-corruption issue.

"Any application that supports embedding Internet Explorer or its scripting engine component may be used as an attack vector for this vulnerability," the CERT Coordination Center at Carnegie Mellon University warned in an advisory, adding that "this vulnerability was detected in exploits in the wild."

The out-of-cycle patch is the third time this year that Microsoft issued a fix for a serious flaw outside of its second-Tuesday-of-the-month schedule, not counting patches for problematic updates. In January, the company patched its code to support firmware updates needed to secure computers against Meltdown and Spectre processor flaws (CVE-2017-5753 and others). In March, Microsoft patched a kernel vulnerability (CVE-2018-1038) introduced during the earlier January update. In May, just a few days before its scheduled patch day, Microsoft issued an update for a vulnerability (CVE-2018-8115) in Windows containers.

In 2003, Microsoft moved away from issuing patches as needed to a monthly patch cycle. While the move seemed to be a way to reduce the number of articles covering the company's frequent software flaws, Microsoft executives argued that deploying patches on a weekly basis caused too much chaos of systems administrators. The company started its monthly patch cycle on October 14, 2003.

This month, Microsoft released its schedule patch on Dec. 11.

In its guidance for the security issue, the company explained that its latest update modifies how Internet Explorer and the scripting engine handles objects in memory. Without the patch, attackers have been able to infect systems using specially crafted scripts.

"In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Internet Explorer and then convince a user to view the website, for example, by sending an email," the company stated in its advisory.

Microsoft did not provide any other explanation, but a spokesperson did issue a comment: "We addressed CVE-2018-8653 and customers who have Windows Update enabled and have applied the latest security updates, are protected automatically," Jeff Jones, senior director at Microsoft, said in a statement.

The scripting engine used by Internet Explorer and Windows has frequently been a source of vulnerability and the vector of attacks and exploits. In May, Microsoft warned of a remote code execution vulnerability in the VBScript engine (CVE-2018-8174), which could be attacked through Internet Explorer or using an ActiveX control in Microsoft Office.

Attackers have often used Office documents with malicious VBScripts to infect systems and get past malware scanners.

The update also continues Microsoft's habit of unwelcome Christmas surprises.

December has always been a month for critical patches in Microsoft products. Last year, for example, Microsoft issued a critical patch for a remote-code execution vulnerability in its Malware Protection Engine, which scans files for potentially malicious code. 

Microsoft credited Clement Lecigne of Google’s Threat Analysis Group with notifying them of the vulnerability's exploitation.

 

Related stories

Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
US Formally Attributes SolarWinds Attack to Russian Intelligence Agency
Jai Vijayan, Contributing Writer,  4/15/2021
News
Dependency Problems Increase for Open Source Components
Robert Lemos, Contributing Writer,  4/14/2021
News
FBI Operation Remotely Removes Web Shells From Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: "Elon, I think our cover's been blown."
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27400
PUBLISHED: 2021-04-22
HashiCorp Vault and Vault Enterprise Cassandra integrations (storage backend and database secrets engine plugin) did not validate TLS certificates when connecting to Cassandra clusters. Fixed in 1.6.4 and 1.7.1
CVE-2021-29653
PUBLISHED: 2021-04-22
HashiCorp Vault and Vault Enterprise 1.5.1 and newer, under certain circumstances, may exclude revoked but unexpired certificates from the CRL. Fixed in 1.5.8, 1.6.4, and 1.7.1.
CVE-2021-30476
PUBLISHED: 2021-04-22
HashiCorp Terraform’s Vault Provider (terraform-provider-vault) did not correctly configure GCE-type bound labels for Vault’s GCP auth method. Fixed in 2.19.1.
CVE-2021-22540
PUBLISHED: 2021-04-22
Bad validation logic in the Dart SDK versions prior to 2.12.3 allow an attacker to use an XSS attack via DOM clobbering. The validation logic in dart:html for creating DOM nodes from text did not sanitize properly when it came across template tags.
CVE-2021-27736
PUBLISHED: 2021-04-22
FusionAuth fusionauth-samlv2 before 0.5.4 allows XXE attacks via a forged AuthnRequest or LogoutRequest because parseFromBytes uses javax.xml.parsers.DocumentBuilderFactory unsafely.