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.

Attacks/Breaches

6/21/2007
08:35 AM
50%
50%

Old Dogs Can Still Do Dirty Tricks

Vulnerabilities can remain dangerous even after they've been discovered and patched

4:35 PM -- "It’s been done before." These are words I hear often when doing my research. You can chalk it up to great minds thinking alike, but it’s frustrating when you think you’re the first -- or at least have a new take on an old issue.

The security industry tends to have a pattern to its madness. Someone discloses a vulnerability, the company who developed the software issues a patch, and the press dies down. But does that pattern really make sense?

I’ve seen vendors patch countless exploits that were extremely dangerous. But what does that mean, exactly? Does that mean the vendor called all its customers, gave them copies of the new software, and insured that they correctly installed the new patch? Doubtful. There are only a few companies that even have automatic patching processes for all of their products, and even those only work if you are using a version of the product that has automatic patching enabled.

So here I sit as a researcher, with thousands of "solved" issues in my brain, looking at a Web application that clearly has a vulnerability -- a vulnerability that has been known for almost 10 years. Does that mean that the issue is no longer there, simply because security researchers have seen it? No. The threat persists because these issues aren’t solved. Just because they are known by a very small group of people doesn’t mean they are solved.

Herein lies the problem. We have security researchers saying it’s not new and vendors saying they’ve long issued a patch, and yet the vulnerability persists. Does that mean it’s less interesting? Perhaps, but that’s irrelevant to the problem at hand. We have vulnerable applications out there that no one has patched -- and without a plan to do so, attackers will always have a way into your network.

It may be "old news," but if you're still vulnerable, it's no less dangerous.

— RSnake is a red-blooded lumberjack whose rants can also be found at Ha.ckers and F*the.net. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest 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...