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.

Security Management //

Patch Management

4/11/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Bastille's ATI System Warning Raises Its Own Alarm

Bastille Networks made a splash by notifying ATI Systems that its warning systems have a significant vulnerability. However, the timing of the notice leaves a question about motives when public safety is at risk.

The ATI Systems, which use sirens to notify the general public in the case of an emergency, are vulnerable to exploitation by unauthorized parties. These kinds of warning systems are in use at locations such as One World Trade Center in New York City and the Indian Point Energy Center nuclear power stations, which are located north of Manhattan.

Discovered by Bastille Network's security researcher Balint Seeber, the attack can happen because encryption is not used in the ATI Systems control protocol. If a bad actor can find the operating frequency of the sirens and craft a malformed packet to act as an activation message, the game is over and the sirens blare.

Bastille first encountered the problem during a security audit of San Francisco's alert system in 2016. However, the company and its researchers did not notify ATI or the city of the potential problem at that time.

However, the company did inform ATI and San Francisco of the vulnerability three months ago, in order to give officials time to put a patch in place. As of this writing that has not happened. That may be due to the difficulty of adapting one patch to the very specific installations that characterize alert systems.

In any case, the patch should be available soon.

In its report, Bastille notes that it is now disclosing the flaw publicly to allow ATI Systems users to determine if their system has the same vulnerability. Researchers are also hoping that other siren vendors will investigate their own systems to patch and fix this type of problem.

In its defense, ATI notes it took Bastille many months of investigation in order to figure out how to do this sort of attack and that it was not a simple matter.

Further, ATI points to the fact that the San Francisco installation is 14 years old and uses a control protocol that is not present in its current products. Even so, a secured system may be too expensive for municipal use.

The use of radio technology in overall alert systems is an interesting corner. But considering that Bastille could have informed San Francisco two years ago about this vulnerability must raise eyebrows about its motivation.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

If at the time Bastille believed that this presented a clear danger to the public, its lack of communication was irresponsible. Even if the company's researchers were waiting for confirmation -- like the sirens going off in Dallas a year ago -- they could have spoken out sooner.

Because of this, as well as Bastille giving the exploit an snappy name --SirenJack -- and a dedicated website, one must ask whether or not this is a way for Bastille to try and gain some publicity by cynically piggybacking onto public fears and anxiety.

Also, by announcing the attack before a patch is available, the company is breaking the principles of responsible disclosure. Such a course of action throws Bastille's motivations into question as well.

Yes, ATI and government officials should patch their older systems, but Bastille is no knight in shining armor in this situation.

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