Attacks/Breaches

8/10/2015
02:35 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Kaminsky Creates Clickjacking-Killer

Famed white-hat hacker proposes a fix for longtime Web attack vector.

DEF CON 23 -- Las Vegas -- Renowned security expert Dan Kaminsky here this week unveiled his latest project: a solution to eradicate so-called clickjacking attacks that plague the Web.

Kaminsky hopes to have his IronFrame approach support the World Wide Web Consortium's (W3C) UI Security specification, and ultimately ensure that clicking on compromised ads and other outside content on a website doesn't silently redirect users to malicious websites in clickjacking attacks. Clickjacking is where concealed and malicious content and links on a website are layered atop legitimate ones, unbeknownst to the user and the website operator.

"We have this problem where, because of the Web security model, you don't actually know what's on your web page. You just pull resources in from around the Net," Kaminsky said in an interview prior to his DEF CON 23 presentation here. "This [content] might be good, bad; maybe … by someone modifying it. This entire class of attacks is called clickjacking."

With IronFrame, Kaminsky says he's using the browser's "graphics model to present the right stuff to the user" rather than the modified content injected by cyber criminals. A PayPal box saying "Want to spend $1000?" could be altered with an icon atop it that changes the link to say $1, for example, he says.

IronFrame operates like a Jenga building-block model, moving the bottom layer of graphics content to the top layer so the browser doesn't even see the phony and malicious layer. It’s a way to end clickjacking "by design," he says.

"It's never been clear how to efficiently validate what the user sees" on the page, he says. "What I'm showing is that if you move the obscured layer to the top of the stack -- after JavaScript but before the GPU -- you can know what the user sees."

The browser to date doesn't even necessarily know what content is being presented to the user, he says. "The browser says, 'hey, GPU: go render this and you figure it out,'" Kaminsky explains.

Kaminsky's solution basically ensures that the original content is rendered by the browser, not any content layered atop it by bad guys.

Kaminsky, who is chief scientist with WhiteOps Security, also built a JavaScript-based CPU monitor that illuminates how when web pages load slowly, it's often due to content hidden within a rogue iFrame.

"Hackers can fix things. We don't just break things," he says. "I like looking at how things actually work and taking that knowledge and using it to make things better.

"We're hackers: we're not afraid to get into how things work. Let's use that knowledge and fearlessness and make things work better," he says.

Kaminsky says his open-source project is in the early stages. "I don't have it perfectly"  yet, he says.

"My goal is to go to a Blink developer [for example] and say we need this, it's feasible, here's a string, a beginning" to build on, he says.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
8/11/2015 | 12:57:35 PM
Re: Clickjacking Killer
Thank you for sharing that insight and perspective, @carofer. It's great to hear from the dev side on this!
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
8/11/2015 | 12:51:53 PM
Clickjacking
Clickjacking is all too prevalent. It's good to see that we are analyzing methods of negating its detrimental effects. Most often this catches non-tech individuals off guard and sometimes even the occassional techie.
carofer
50%
50%
carofer,
User Rank: Apprentice
8/11/2015 | 12:46:15 PM
Clickjacking Killer
It has disturbed me, as a manager of developers, that heavy-handed security restrictions like CORS are invented to thwart exploits like clickjackings. The honest developer is left with the task of working around the restrictions in order to provide mash-ups or other multi-domain user experiences.  It has a very high cost for developers, and, when workarounds such as JSONP are used, the original goals of the restriction are completely defeated, making it all a huge exercise in futility.

The development of the Kaminsky solution is therefore of HUGE significance, and we practitioners welcome it.

Bring it on and maybe we can be done with the kabuki dance of (some) porous security standards!!!

Allan Rofer
Devastating Cyberattack on Email Provider Destroys 18 Years of Data
Jai Vijayan, Freelance writer,  2/12/2019
Up to 100,000 Reported Affected in Landmark White Data Breach
Kelly Sheridan, Staff Editor, Dark Reading,  2/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8354
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c has an integer overflow on the result of multiplication fed into malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow.
CVE-2019-8355
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. In xmalloc.h, there is an integer overflow on the result of multiplication fed into the lsx_valloc macro that wraps malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow in channels_start in remix.c.
CVE-2019-8356
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. One of the arguments to bitrv2 in fft4g.c is not guarded, such that it can lead to write access outside of the statically declared array, aka a stack-based buffer overflow.
CVE-2019-8357
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c allows a NULL pointer dereference.
CVE-2013-2516
PUBLISHED: 2019-02-15
Vulnerability in FileUtils v0.7, Ruby Gem Fileutils <= v0.7 Command Injection vulnerability in user supplied url variable that is passed to the shell.