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.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-46547
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via /usr/local/bin/mjs+0x2c17e. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46548
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via add_lineno_map_item at src/mjs_bcode.c. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46549
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via parse_cval_type at src/mjs_ffi.c. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46550
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via free_json_frame at src/mjs_json.c. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46553
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via mjs_set_internal at src/mjs_object.c. This vulnerability can lead to a Denial of Service (DoS).