IoT

Researcher Cracks San Francisco's Emergency Siren System

100%
0%

Bastille's director of vulnerability research, Balint Seeber discusses the process of creating SirenJack and cracking one of a city's critical safety systems. Filmed at Dark Reading News Desk at Black Hat USA 2018.

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
donaldrobbinss
50%
50%
donaldrobbinss,
User Rank: Apprentice
11/3/2018 | 1:41:14 PM
Re: Good man, pointing out weak security.
like
A96.uk
100%
0%
A96.uk,
User Rank: Apprentice
8/28/2018 | 3:15:38 AM
Good man, pointing out weak security.
I also showed how to clone on TTN with LoRaWAN a year or two back.

LoRaWAN uses very poor secuirty using symmetric keys when asymmetric in hardware is required.

Massive IoT systems have been deployeed all over the world using this very poor security.

Cloning is easy and the current system does not know the difference.

TTN forum people could not understand what i was showing them, all fools.

 

I told the VP of Semtech about this and they sent me £2000 of kit to test.

LoRaWAN security design is broken, but they all dont want to talk about it.

 

I think the NSA told LoRaWAN design team , they must have access to all IoT devices & AES keys.

So now they have a database of AES keys!

I told them no one in security stores AES keys in a database.

 

I pointed to SAML11 for their education and the 508a/608a from Microchip.

 

Now most people using LoRaWAN think its safe as they are all sheep.

They all trust software security far to much, like idiot's they all are.

 

If only a BLACK HAT researcher would look into LoRaWAN security!

I have only 30 years experience under my belt, i used to work for bank security also.

 
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8980
PUBLISHED: 2019-02-21
A memory leak in the kernel_read_file function in fs/exec.c in the Linux kernel through 4.20.11 allows attackers to cause a denial of service (memory consumption) by triggering vfs_read failures.
CVE-2019-8979
PUBLISHED: 2019-02-21
Koseven through 3.3.9, and Kohana through 3.3.6, has SQL Injection when the order_by() parameter can be controlled.
CVE-2013-7469
PUBLISHED: 2019-02-21
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
CVE-2018-20146
PUBLISHED: 2019-02-21
An issue was discovered in Liquidware ProfileUnity before 6.8.0 with Liquidware FlexApp before 6.8.0. A local user could obtain administrator rights, as demonstrated by use of PowerShell.
CVE-2019-5727
PUBLISHED: 2019-02-21
Splunk Web in Splunk Enterprise 6.5.x before 6.5.5, 6.4.x before 6.4.9, 6.3.x before 6.3.12, 6.2.x before 6.2.14, 6.1.x before 6.1.14, and 6.0.x before 6.0.15 and Splunk Light before 6.6.0 has Persistent XSS, aka SPL-138827.