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.

Operations

11/17/2016
06:15 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

As Deadline Looms, 35 Percent Of Web Sites Still Rely On SHA-1

Over 60 million web sites are relying on a hashing algorithm that will be blocked by major browsers starting Jan 1.

A surprising 35 percent of websites around the world are still using SHA-1 though barely 45 days remain before some of the major browsers stop trusting certificates signed with the hash algorithm altogether.

The estimate, from cybersecurity vendor Venafi, is based on an analysis of data from some 11 million publicly visible websites.

The analysis showed that while most of the popular websites have migrated away from SHA-1, a troublingly large number has not. Based on recent numbers from Netcraft showing over 173 million active websites on the Internet, Venafi extrapolated its results to mean there are about 61 million sites that rely on the deprecated certificates.

Such sites can expect transactions and traffic to be disrupted in multiple ways starting January 1, 2017. Google, for instance, has said that its Chrome browser will drop all support for SHA-1 certificates starting that date. Chrome will block all certificates signed with the algorithm triggering a fatal network error, Google has previously warned.

Like Mozilla and the others, Google stopped treating SHA-1 certificates as secure a long time ago, and has been discontinuing support for it in a phased manner. Starting earlier this year, Chrome has displayed a certificate error warning for sites using SHA-1 certificates that were issued on or after January 1, 2016. That is the date before which all certificate authorities were supposed to stop issuing SHA-1 certificates.

Through the year, Google has been ramping up those warnings with a view to weaning websites off SHA-1 completely by the end of this year.

Others have been following a similar approach. Starting with Windows 10 Anniversary Update, Microsoft’s Edge and Internet Explorer browsers have been removing the address bar lock icon on sites relying on SHA-1. Though the sites have continued to work, the browsers no longer consider them to be secure. That will change further in Feb 2017 when both browsers will block SHA-1-signed certificates altogether.

The moves by the browser makers are a response to long-standing concerns over SHA-1 security. Noted security researchers such as cryptography expert Bruce Schneier have warned about SHA-1 being vulnerable to collision attacks — where two messages generate the same hash value — as  far back as 2005.

Last year, researchers from the national research institute for math and computer science in the Netherlands, France’s Inria, and the Nayang Technology University in Singapore, showed how a full-scale collision attack on SHA-1 could be carried out for about $100,000 using cloud based hardware. The research showed that attacks against SHA-1 were not only possible sooner than most experts had anticipated, but also could be performed at much lower cost as well.

The transition deadline for SHA-1 is long overdue, says Kevin Bocek, vice president of security strategy and threat intelligence at Venafi. The National Institute of Standards and Technology called for the elimination of SHA-1 in 2006, over security concerns, he notes.

“Successful attacks on SHA-1 are well within reach of nation states and other sophisticated adversaries, and these allow them to ‘mint’ trusted SHA-1 certificates,” Bocek says.

As one example of the damage that can be caused by such certificate counterfeiting, Bocek points to a 2012 incident where attackers were able to widely distribute the Flame malware sample using forged Microsoft MD5 certificates.

The key to getting rid of SHA-1 certificates is figuring out how and where they are being used, he says. Large organizations are especially likely to have little visibility over the extent to which such certificates are being used, and need to have a plan for discovering and eliminating them, he says.

Related stories:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... 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...