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.

Vulnerabilities / Threats

6/21/2017
07:15 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

'Stack Clash' Smashed Security Fix in Linux

Linux, OpenBSD, Free BSD, Solaris security updates available to thwart newly discovered attack by researchers.

What's old is new again: an exploit protection mechanism for a known flaw in the Linux kernel has fallen to a new attack targeting an old problem.

The so-called Stack Clash vulnerability, which was discovered and disclosed by Qualys, affects Linux, OpenBSD, NetBSD, FreeBSD, and Solaris, on i386 and amd64 processors. These platforms earlier this week received patches for the vulnerability, a memory management flaw in the Linux kernel that could allow attackers to bypass security controls previously put in place to prevent memory management attacks on Linux-based servers, appliances, and even Internet of Things devices.

Qualys developed seven exploits and proof-of-concepts to demonstrate the vulnerability, which could be used by an attacker to corrupt memory and run malicious code and ultimately gain control of a targeted machine. Researchers at Qualys are urging organizations to update their Linux plaforms immediately for the flaw.

"It [the flaw] has to do with the memory management of these systems, so it's widespread in terms of scope," says Jimmy Graham, director of the product protection team at Qualys. Graham says it allows a privilege escalation-type attack.

What makes this particular vulnerability unique is that it bypasses controls and mitigations that Linux developers put in place to prevent memory-management attacks. "It shows that the specific mitigation is not effective," he says.

The attack that StackClash executes really isn't new: The concept of the memory management/pressure attack was first employed by researchers in 2005, and again in 2010. Linux developers responded to those disclosures with the so-called StackGuard Page security mitigation for the operating system - which Stack Clash cheats. "We bypassed StackGuard Page … to jump into [Linux] memory," Graham notes.

Stack Clash, which require local access to the targeted Linux machine, works like this: it overwrites a region in the kernel memory called the stack, causing confusion in the memory and allowing an attacker to "clash" with another memory region. Qualys researchers used local privilege escalation exploits against the flaw to gain full root privileges to the targeted system.

What makes the attack especially dangerous is that it can be "chained" with another vulnerability to escalate into a deeper and more pervasive attack. An attacker could employ SQL injection as well and escalate the attack to reach other shared systems in the victim organization, according to Qualys, specifically in shared, multi-tenant systems.

"This affects any kind of Linux or BSD system – appliances to back-end equipment to Web servers," Graham says.

Don Bailey, founder and CEO of Lab Mouse Security, says while these memory pressure vulnerabilities have been well-documented, Stack Clash demonstrates just how widely these flaws can be exploited by attackers.

"The design of the operating system and how it reacts to memory pressure: that's fascinating research. This opens a whole new world of embedded systems that rely on Linux … which can be vulnerable as well to this style of attacks," he says. And the obvious problem of little or no patching of embedded systems puts them even more at risk.

While Stack Clash is a local attack, Qualys researchers haven't ruled out the possibility of remote attacks via the flaw as well.

"Our research has mainly focused on local exploitation: as of this writing on June 19, 2017, we do not know of any remotely exploitable application. However, remote exploitation of the Stack Clash is not excluded; although local exploitation will always be easier, and remote exploitation will be very application-specific," Qualys wrote in a blog post on the attack.

Qualys also published technical details on Stack Clash (CVE-2017-1000364), in a security advisory as well as related flaws CVE-2017-1000365), and CVE-2017-1000367).

Related Content:

Black Hat USA returns to the fabulous Mandalay Bay in Las Vegas, Nevada, July 22-27, 2017. Click for information on the conference schedule and to register.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...