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.

Comments
Solving IPTV's Security Problem
Newest First  |  Oldest First  |  Threaded View
RichardB125
50%
50%
RichardB125,
User Rank: Apprentice
6/9/2017 | 9:33:58 PM
Denial of Service attacks
In reading this article, I have to concurr that security is and must be paramount.

I started to experience these problems at home more than a year ago. One of my sons got a Roku box and later NVidia media shield.

Many times we had been attacked and cut of the internet services only when using any of these two boxes. Started with a massive DoS that somehow poisoned the CAM table of the managed switch. As we do not have any VLANS or separate network for Roku or NVidia boxes, it ended up corrupting and cutting of the internet services as the exit gateway on any PC at home ends in 0.0.0.0 instead of the right one. It also poisons the DNS cache of the home router.

After that I put in service a Cisco ASA 5506x- Firepower and things turned more difficult for them.

Two weeks ago I took the Cisco ASA out and put a Fortinet 30E but forgot to enable the DoS policy, hence, last night we lost the internet again but now the policy is in place, as well as IPS (Intrusion Prevention System). Needeles to say this weekend, the NVidia shield will end in its own Vlan and VDOM (as fortigate callst it) and in a new managed switch with ARP protection as well.

Well, not many home users will have the knowkedge and capacity to put this toghether but let me tell you that 99% oh those "royuters" at home would not last 10 seconds. Even some of the "commercial" grades one like D Link D 520 that I had to put in the rubbish bin.

Yes, agree, there is a gigantic problem..............I can even see the security logs of the Fortigate 30E with the HTTP injection coming in...............quite an incredible and "invisible to the human eyes" problem.


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...