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

10:15 AM
Larry Loeb
Larry Loeb
Larry Loeb

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.

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
Newest First  |  Oldest First  |  Threaded View
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This is not what I meant by "I would like to share some desk space"
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-01-20
This affects the package com.softwaremill.akka-http-session:core_2.12 from 0 and before 0.6.1; all versions of package com.softwaremill.akka-http-session:core_2.11; the package com.softwaremill.akka-http-session:core_2.13 from 0 and before 0.6.1. CSRF protection can be bypassed by forging a request ...
PUBLISHED: 2021-01-20
This affects all versions of package github.com/gin-gonic/gin. When gin is exposed directly to the internet, a client's IP can be spoofed by setting the X-Forwarded-For header.
PUBLISHED: 2021-01-20
Keymaker is a Mastodon Community Finder based Matrix Community serverlist page Server. In Keymaker before version 0.2.0, the assets endpoint did not check for the extension. The rust `join` method without checking user input might have made it abe to do a Path Traversal attack causing to read more f...
PUBLISHED: 2021-01-20
A flaw was found in dnsmasq before version 2.83. When receiving a query, dnsmasq does not check for an existing pending request for the same name and forwards a new request. By default, a maximum of 150 pending queries can be sent to upstream servers, so there can be at most 150 queries for the same...
PUBLISHED: 2021-01-20
A flaw was found in dnsmasq before version 2.83. A heap-based buffer overflow was discovered in dnsmasq when DNSSEC is enabled and before it validates the received DNS entries. This flaw allows a remote attacker, who can create valid DNS replies, to cause an overflow in a heap-allocated memory. This...