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

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
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
How Enterprises are Attacking the Cybersecurity Problem
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-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.
CVE-2019-20391
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20392
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20393
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.