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.

Endpoint Security

// // //
1/1/2018
04:15 PM
Larry Loeb
Larry Loeb
Larry Loeb

Chain of Flaws Threatens Win 10

Chaining multiple vulnerabilities can create attacks that threaten millions of Windows 10 computers.

An attack on a computer system usually tries to knock something over and bypass that one thing. But that is not always the case. Sometimes, the attack can involve chaining a number of problem together to gain the final vulnerability.

Google's Project Zero found just such a complex chain can occur in Windows. They wrote in their blog about an attack that ends up allowing untrusted JavaScript to run outside a sandbox on a fully patched 64-bit Windows 10 system.

{Imag 1}

The method that they found was a variation of a Web Proxy Auto Discovery Protocol/Proxy Auto-Config (WPAD/PAC) attack. If those terms look unfamiliar to you, you aren't alone. They are artifacts of early internet efforts to make seamless connections. PAC was a way for JavaScript to find a server it could download a configuration file from, and WPAD a way to query a local network for where the PAC file could be found. When this is combined with vulnerabilities of the Microsoft JScript.dll file, all sorts of trouble ensues.

WPAD has been a previous attack vector which can allow an threat actor to monitor the URL of every site a browser visits, even if it has been protected with HTTPS encryption. But the Project Zero researchers took things even further in what they achieved, which is a total compromise of the target machine.

First, they chained two JScript bugs (namely an infoleak as well as a heap overflow) and then included other tricks (return-oriented programming for one) to bypass Windows security mitigations. They then escalated the process from local, where WPAD lives, to system.

The researchers also found an interesting memory read primitive (out-of-bounds read) that they used in this effort that may have nefarious use in other attack situations.

Microsoft has patched the bugs the researchers have found, but that does not mean that everyone can relax. As they put it, "Since the bugs are now fixed, does this mean we are done and can go home? Unlikely. Although we spent a fair amount of time, effort and compute power on finding jscript.dll bugs, we make no claims that we found all of them. In fact, where there are 7 bugs, there is likely to be an 8th."

They do recommend that users disable the WPAD service by default as well as sandbox the JScript interpreter inside the WPAD service. But your average user is not going to be able to do that.

The situation shows how methods and efforts that may have possibly been useful at one time long ago can serve in combination with other problems to blow a hole in the side of a victim's system. There will come a time when backwards compatibility will have to be sacrificed on the altar of security to avoid these kinds of large gaping wounds.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Developing and Testing an Effective Breach Response Plan
Whether or not a data breach is a disaster for the organization depends on the security team's response and that is based on how the team developed a breach response plan beforehand and if it was thoroughly tested. Inside this report, experts share how to: -understand the technical environment, -determine what types of incidents would trigger the plan, -know which stakeholders need to be notified and how to do so, -develop steps to contain the breach, collect evidence, and initiate recovery.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-46366
PUBLISHED: 2022-12-02
** UNSUPPORTED WHEN ASSIGNED ** Apache Tapestry 3.x allows deserialization of untrusted data, leading to remote code execution. This issue is similar to but distinct from CVE-2020-17531, which applies the the (also unsupported) 4.x version line. NOTE: This vulnerability only affects Apache Tapestry ...
CVE-2022-4270
PUBLISHED: 2022-12-02
Incorrect privilege assignment issue in M-Files Web in M-Files Web versions before 22.5.11436.1 could have changed permissions accidentally.
CVE-2022-2807
PUBLISHED: 2022-12-02
Algan Yazılım Prens Student Information System product has an unauthenticated SQL Injection vulnerability.
CVE-2022-2808
PUBLISHED: 2022-12-02
Algan Yaz?l?m Prens Student Information System product has an authenticated Insecure Direct Object Reference (IDOR) vulnerability.
CVE-2022-44929
PUBLISHED: 2022-12-02
An access control issue in D-Link DVG-G5402SP GE_1.03 allows unauthenticated attackers to escalate privileges via arbitrarily editing VoIP SIB profiles.