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

8/29/2018
04:30 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Windows Zero-Day Flaw Disclosed Via Twitter

Security experts confirm the privilege escalation vulnerability in Microsoft Windows still works.

A previously undisclosed zero-day vulnerability in Microsoft's Windows 10 operating system was published via Twitter this week.

SandboxEscaper, the user behind the Twitter account that exposed the vulnerability, first posted about the bug on Monday, Aug. 27 and linked to a proof-of-concept on GitHub. This is a local privilege escalation vulnerability, which exists in the Advanced Local Procedure Call (ALPC) interface within the Windows Task Manager, reports CERT vulnerability analyst Will Dormann.

An API in the Windows task scheduler contains a vulnerability in the handling of ALPC, and the bug could allow a local user to gain system privileges, Dormann explains in a CERT writeup on the vulnerability.

"We have confirmed that the public exploit code works on 64-bit Windows 10 and Windows Server 2016 systems," Dormann writes. "Compatibility with other Windows version may be possible with modification of the publicly-available exploit source code."

Dormann later posted his own tweet confirming the exploit works even if the Windows 10 64-bit system is fully patched; with minor tweaks, it works on 32-bit systems as well. He is currently unaware of any workaround.

The way this vulnerability was disclosed – with social media posts and a proof-of-concept published on GitHub – has captured the attention of the security community. However, as Synopsys principal scientist Sammy Migues points out, the discovery of a local privilege escalation flaw is "fairly common."

Average users running Windows machines with this vulnerability can exploit it to gain elevated privileges despite not being granted that level of access by IT admins, Migues explains. If they do, anyone who gains access to their device will have the same privileges, putting the device and its data at risk.

He also points out it is possible for remote attackers to exploit this vulnerability, which would typically require local access, if a local user executes the attacker's code via phishing email or downloading malicious software.

"Having a working exploit out in the world makes this easier for everyone," he continues. "A remote attacker would have to get someone to run their attack code," via a phishing attack, for example, he says.

Microsoft has not issued an emergency patch for the bug. The company, which neither confirmed nor denied the existence of this vulnerability, will release its next wave of monthly fixes on September's Patch Tuesday update, which will take place on Sept. 11.

"Windows has a customer commitment to investigate reported security issues, and proactively update impacted devices as soon as possible. Our standard policy is to provide solutions via our current Update Tuesday schedule," reported a Microsoft spokesperson.

Related Content:

 

Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27225
PUBLISHED: 2021-03-01
In Dataiku DSS before 8.0.6, insufficient access control in the Jupyter notebooks integration allows users (who have coding permissions) to read and overwrite notebooks in projects that they are not authorized to access.
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.