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

11/1/2017
04:18 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

WannaCry Was an Avoidable Mess for NHS

A new report says that the UK's NHS could have avoided WannaCry entirely. Is it possible to secure a network from the ravages of bottom-line focused management?

How much security can technology provide? More to the point, how much insecurity can technology overcome? It's the kind of question that makes entrepreneurs dream and executives worry.

The great divide between technology and practice has been newly illuminated by a report on the National Audit Office's investigation of the WannaCry attack that hit the National Health Service. Here's the shocking news: It could have been stopped.

Now, anyone who followed WannaCry, how it spread and what it did, knows that millions of organizations around the world were not hit by the attack because of the operating systems they use or precautions they had taken. In the case of the NHS, it turns out that they were vulnerable and knew they were vulnerable at least a year before WannaCry.

The service had begun to respond, but the response was a variation on the old management favorite, "We'll fix it when we eventually replace the systems now using vulnerable software." Unfortunately for the NHS and at least a few thousand of its patients, WannaCry didn't wait for "eventually."

A decision to remediate by replacement, and wait until the normal refresh cycle plays out to replace, is a management decision, not a security team decision. And it is, let me emphasize, a decision based on money. Most security decisions are, at their core, motivated by money, but in this case it was a gamble that was lost in very public fashion.

Let's all admit something: If we knew -- really knew -- that every piece of hardware and software attached to the network was fully patched and up to date, and that every application was written to best practices standards for robust, secure behavior, then there is a great deal of funding currently sent to security spending that could go elsewhere. A non-trivial fraction of our total security spending goes to papering over holes that we are confident exist in our applications and infrastructure.

In talking with engineers, developers and security researchers it has become obvious that there is a great deal of development going on that is intended to, in blunt terms, protect us from ourselves. We want to be secure, but we don't want any "friction" in our transactions. We want our systems to be safe, but we don't want to take the time to test systems for security. We want to have secure applications, but we demand that they be updated hourly while hoping they'll be safe.

Throughout all of this we have to come face to face with the limits of technology. Security systems are becoming more capable, more flexible and faster, but they are constantly running up against failures in policy, process and human behavior. The day may come when scientists give enterprise networks at least a temporary advantage over the criminals who want to get in. I'm not convinced that we will ever have designs that keep us in front of short-sighted decision-making and ill-considered behavior for any meaningful length of time.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

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