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.

Application Security //

Web Application Development

2/14/2018
10:15 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Mozilla Leads the Way to Safer Browser Development

Mozilla is looking to make web browsers safer by adding new developer features into Firefox that should make the HTTPS protocol a must-have way to transmit for websites.

In a welcome and long overdue change in direction, browser creators are starting to look at the features that developers include in their code with an eye to security.

Mozilla was the first out of the chute on Monday by announcing that the Application Cache feature of HTML5 will not be working if the information transfer between browser and site does not occur as HTTPS.

Application Cache or AppCache lets developers specify which parts of the site will be available to the users offline. The idea is to give extra functionality to users, improve browser speed and reduce the effective load.

However, there are concomitant security risks when used with HTTP alone. Because the cache is not revalidated in use, malicious content can be loaded in a Man-in-the-Middle type of attack and viewed indefinitely even when the user is offline.

(Source: Wikipedia)
(Source: Wikipedia)

On a non-secured WiFi network, for instance, Johnathan Kingston describes in the Mozilla blog how this attack would work:

Even if the user only visits one HTTP page over the WiFi, the attacker can plant many insecure iframes using AppCache which allows the attacker to rig the cache with malicious content manipulating all of those sites indefinitely. Even a cautious user who decides only to login to their websites at home is at risk due to this stale cache.

This is a potentially huge attack vector, as can be seen.

Kingston goes on to describe what Mozilla is going to do about this. He writes that in Firefox 60+ Beta and Nightly, Application Cache access from HTTP pages will be denied. Not only that, but starting with May's Firefox 62 release, Application Cache over HTTP will be fully removed for all the release channels.

Mozilla is serious about the effort, as are other browser makers. In fact, Chrome, Edge and WebKit have also stated their intent to remove this feature when used over HTTP. This will end up changed in the HTTP standardas well.

This fits in with Mozilla's avowed intention to deprecate HTTP and requiring HTTPS for all new APIs. Not only that, they will be stalwart in their effort to remove features from sites that are served over insecure connections.

The upshot of this effort by all the browser makers is that websites that want to preserve their functionality need to transition to the use of TLS encryption soon. If they don't, these kinds of API depreciations will end up taking their functionality away from them.

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
Newest First  |  Oldest 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
Enterprise Cybersecurity Plans in a Post-Pandemic World
Download the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3806
PUBLISHED: 2021-09-18
A path traversal vulnerability on Pardus Software Center's "extractArchive" function could allow anyone on the same network to do a man-in-the-middle and write files on the system.
CVE-2021-41392
PUBLISHED: 2021-09-17
static/main-preload.js in Boost Note through 0.22.0 allows remote command execution. A remote attacker may send a crafted IPC message to the exposed vulnerable ipcRenderer IPC interface, which invokes the dangerous openExternal Electron API.
CVE-2020-21547
PUBLISHED: 2021-09-17
Libsixel 1.8.2 contains a heap-based buffer overflow in the dither_func_fs function in tosixel.c.
CVE-2020-21548
PUBLISHED: 2021-09-17
Libsixel 1.8.3 contains a heap-based buffer overflow in the sixel_encode_highcolor function in tosixel.c.
CVE-2021-39218
PUBLISHED: 2021-09-17
Wasmtime is an open source runtime for WebAssembly & WASI. In Wasmtime from version 0.26.0 and before version 0.30.0 is affected by a memory unsoundness vulnerability. There was an invalid free and out-of-bounds read and write bug when running Wasm that uses `externref`s in Wasmtime. To trigger ...