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.

Operational Security

1/14/2019
08:15 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

US Government Shutdown Preventing SSL Certificates From Being Renewed

The shutdown of the federal government is not only affecting federal workers, but the websites that various departments run. Specifically, SSL certificates are not being renewed.

The shutdown of the US government -- the longest ever -- is starting to affect more than the 800,000 federal workers who have either been furloughed during this time or told to show up to work but without pay.

As a consequence of these locked-out workers not being at their posts, the SSL certificates used by various government websites that have expired have not been renewed. This lack of certificates can mean that sites or no longer reachable, or they are marked as insecure in their connections.

Sites including the US Justice Department, NASA -- not the main site but some subdomains such as https://rockettest.nasa.gov/ -- and the US Court of Appeals are affected by the lack of over 80 TLS certificates that are used on .gov domains.

The DoJ's https://ows2.usdoj.gov/ is a good example of the problem. Since the site is on Chromium's HTTP Strict Transport Security (HSTS) preload list, the website becomes inaccessible. This is because both Google Chrome and Mozilla Firefox will hide the button -- as HSTS calls for -- that enables users to temporarily ignore the warning about the lack of the TLS system and contact the website.

Other browsers generally use the Chrome preload list as the basis of their own preload lists, so there is no workaround for the HSTS situation on these sites by using other browsers.

GlobalSign notes in a company blog post that expiring TLS certificates can have negative consequences for an enterprise or a government agency. The list of issues includes:

Website Owner: Reduction in trust as the site becomes unsecure; decline in sales and revenue with increased shopping basket abandonments; corporate brand and reputation adversely affected putting the business at risk

In addition:

Website User: Warning error messages displayed by browsers when visiting the site; personal information at risk from man-in-the-middle attacks; individual susceptible to fraud and identity theft

Doug Beattie, GlobalSign's vice president of Product Management, also notes on the company's blog: "We predict that over 600 SSL Certificates currently securing a .gov domain due to expire in October will be potentially affected. To minimize the impact, current automated SSL Certificate life cycle management tools can help in terms of best practice when managing SSL reliance during unforeseen outages."

The shutdown also causes another kind of problem. The sites themselves, whether their certs have expired or not, may not be maintained. Inaccurate or outdated information is likely to be present along with a reduced functionality.

There is little question that the security of the .gov sites will suffer without a valid TLS certificate. In a blog, security vendor Netcraft notes that only a small proportion of .gov sites attempt to set an additional access policy through the Strict-Transport-Security HTTP header. Even if these policies are established they will not be obeyed when they are served alongside an expired certificate.

However, they may be effective if the user has already visited the sites.

With the government IT infrastructure unattended, the shutdown also presents a window for hostile actors to try and infiltrate the .gov infrastructure.

Despite the political arguments the shutdown represents, the practical effect of it is to lessen the security and well-being of anyone that uses the computer systems the government operates.

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
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...