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

10/10/2012
02:33 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Web API Allows Phishing Attack

A recent addition to HTML5, the Fullscreen API, appears to be easily abused.

11 Security Sights Seen Only At Black Hat
11 Security Sights Seen Only At Black Hat
(click image for larger view and for slideshow)
A proof-of-concept phishing attack designed by a Stanford computer science graduate student offers a reminder that new Web technology can reinvigorate old risks.

Feross Aboukhadijeh, a Web designer, developer, and computer security researcher, has developed a way to spoof websites using the relatively new HTML5 Fullscreen API. As its name suggests, the API allows Web developers to present content in full-screen mode, without the distractions of Web browser interface elements.

Aboukhadijeh has published details of the attack on his website, which includes a link that opens a fake Bank of America page to demonstrate the technique. The attack uses the Fullscreen API to hide the interface elements of the user's browser--the chrome and the URL address bar--beneath an image of those interface elements. This prevents the user from knowing which website he is visiting.

Browser vendors have been aware of the potential for using this API for spoofing since it was first proposed. The Fullscreen API specification includes a "Security and Privacy Considerations" section that advises browser makers to implement an overlay element that tells the end user when full-screen mode has been initiated. "This is to prevent a site from spoofing the end user by recreating the user agent or even operating system environment when fullscreen," the specification states.

[ Read Why Huawei Has Congress Worried. ]

Unfortunately, Apple's Safari browser, version 6.01 and later, provides little or no sign that full-screen mode has been activated. Google Chrome, version 22 and later, offers some notice, though as Aboukhadijeh observes, the notification is "pretty subtle and easily missed." Mozilla Firefox, version 10 and later, alerts the user with a conspicuous notification.

Microsoft Internet Explorer 10 does not presently support the HTML5 Fullscreen API, although IE under Windows 8's Metro interface is always full screen. Microsoft confronted the issue of browser UI abuse in 2004 and placed constraints on chromeless popup windows in its Windows XP SP2 update to reduce the risk of spoofing.

Aboukhadijeh's attack depends on social engineering rather than flawed code. Although it's certainly less worrisome than a technical vulnerability that could allow the remote takeover of a computer, it's also less easily fixed--human gullibility can't be patched and defining adequate notification for an interface change isn't as simple as modifying code to prevent a crash.

There are a variety of ways to deceive people online and the only way to mitigate that risk is constant vigilance. In Apple's case, following the security recommendations in Fullscreen API specification would help, too.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
PJS880
50%
50%
PJS880,
User Rank: Ninja
10/15/2012 | 9:19:07 AM
re: Web API Allows Phishing Attack
I love reading about security exploits in information technology. Way to go Doubleheader for locating and sharing the exploit and now it is being properly addressed. With small warning that are easily overlooked it is surprising that these are not more common today than ever before due to the presence of HTML5 on the web. Disappointing to read that this was clearly addressed under securities and not brought more to the forefront as a much larger vulnerability than outlined.

Paul Sprague
InformationWeek Contributor
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-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.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...