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
Fixing IoT Security: Dark Reading Radio Wednesday at 1 P.M. ET
Newest First  |  Oldest First  |  Threaded View
lynnbr2
50%
50%
lynnbr2,
User Rank: Strategist
9/23/2015 | 9:41:39 AM
Why consumers should own the software on products they buy
Sharing the editorial at the link below:

www dot designworldonline dot com/the-real-reason-manufacturers-dont-want-consumers-to-own-software/ 

 
Austin Milbarge
100%
0%
Austin Milbarge,
User Rank: Apprentice
9/23/2015 | 9:35:16 AM
couple of questions
It's awesome that folks in IT security are making such a great effort to work with the various IoT companies etc as it's a Pandora's Box that needs to be addressed.

That said....

Q1 - I'm curious though if there are any initiatives in the works to work with these IoT companies when it comes to interacting with security researchers (outside said company/ies), their response and reaction to bugs, exploits, zero days etc that are brought to their attention especially in good faith. 

And

Q2 - Once informed, how to categorize and address the disclosed issue within the company. Is it a "stop everything and get this fixed asap" issue because said company may have early beta equipment in-use in the wild (customers) and may feel the issue is enough of a threat to apply most of their resources to fixing said issue (at least those resources necessary to address the issue) even if it means taking those resources away from their current work (perhaps in the midst of meeting a deadline?) I realize it's all contextual and we could all come up with 100 different scenarios but it should be noted that a lot of start-ups are going to be riding a fine line with deadlines, money, perception etc and likely won't be able to weather a misstep quite as well as the larger more established companies.


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-2021-23270
PUBLISHED: 2021-04-12
In Gargoyle OS 1.12.0, when IPv6 is used, a routing loop can occur that generates excessive network traffic between an affected device and its upstream ISP's router. This occurs when a link prefix route points to a point-to-point link, a destination IPv6 address belongs to the prefix and is not a lo...
CVE-2021-29302
PUBLISHED: 2021-04-12
TP-Link TL-WR802N(US), Archer_C50v5_US v4_200 <= 2020.06 contains a buffer overflow vulnerability in the httpd process in the body message. The attack vector is: The attacker can get shell of the router by sending a message through the network, which may lead to remote code execution.
CVE-2021-29357
PUBLISHED: 2021-04-12
The ECT Provider component in OutSystems Platform Server 10 before 10.0.1104.0 and 11 before 11.9.0 (and LifeTime management console before 11.7.0) allows SSRF for arbitrary outbound HTTP requests.
CVE-2021-3125
PUBLISHED: 2021-04-12
In TP-Link TL-XDR3230 < 1.0.12, TL-XDR1850 < 1.0.9, TL-XDR1860 < 1.0.14, TL-XDR3250 < 1.0.2, TL-XDR6060 Turbo < 1.1.8, TL-XDR5430 < 1.0.11, and possibly others, when IPv6 is used, a routing loop can occur that generates excessive network traffic between an affected device and its u...
CVE-2021-3128
PUBLISHED: 2021-04-12
In ASUS RT-AX3000, ZenWiFi AX (XT8), RT-AX88U, and other ASUS routers with firmware < 3.0.0.4.386.42095 or < 9.0.0.4.386.41994, when IPv6 is used, a routing loop can occur that generates excessive network traffic between an affected device and its upstream ISP's router. This occurs when a link...