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
Hacking Factory Robot Arms for Sabotage, Fun & Profit
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
7/4/2017 | 10:32:44 AM
Re: Tech is Tech is Tech
@Christian: You raise excellent points -- and I don't see any of this changing as long as "first to market, first to market, first to market" remains the battle cry of global industry.
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
7/4/2017 | 10:31:41 AM
Alternatively, violence
Alternatively, a dastardly hacker who cares less for subtlety and "the long game" could potentially hack into those big yellow robotic arms to cause massive devastation and even hurt people.

Comic book idea: Hacker introduces micro-defect, blackmails company engineer, company engineer pays up, and before company engineer can fix the problem, hacker uses IIoT hack to kill the company engineer. Rinse and repeat.
RetiredUser
0%
100%
RetiredUser,
User Rank: Ninja
6/30/2017 | 12:15:42 PM
Tech is Tech is Tech
Not to get repetitive, but tech is tech is tech.  All I can say to this is that, if you make an electronic device that has parts that can "talk" to other parts, or has an interface that can be "talked" to in any way, and that device controls something, assume it can and will be hacked, cracked, etc.

Hacking {Fill in Your Product} for Sabotage, Fun & Profit should be the very first document written before a product even goes to the Testing team.  The more exploits discovered in Dev the better; putting anything out in Prod (especially manufacturing and hospital robotics) that can be hacked in this first weeks of Production use shows limited concern for the end user, the company as a whole and the industry.

As interesting as all these studies and guidelines are, they all point to the same trend.  That trend is a too-loose security and software methodology and regulatory environment that encourages - no, mandates - more aggressive product security development and risk analysis.

 

 

 


More SolarWinds Attack Details Emerge
Kelly Jackson Higgins, Executive Editor at Dark Reading,  1/12/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4873
PUBLISHED: 2021-01-19
IBM Planning Analytics 2.0 could allow an attacker to obtain sensitive information due to an overly permissive CORS policy. IBM X-Force ID: 190836.
CVE-2020-4881
PUBLISHED: 2021-01-19
IBM Planning Analytics 2.0 could allow a remote attacker to obtain sensitive information, caused by the lack of server hostname verification for SSL/TLS communication. By sending a specially-crafted request, an attacker could exploit this vulnerability to obtain sensitive information. IBM X-Force ID...
CVE-2021-22498
PUBLISHED: 2021-01-19
XML External Entity Injection vulnerability in Micro Focus Application Lifecycle Management (Previously known as Quality Center) product. The vulnerability affects versions 12.x, 12.60 Patch 5 and earlier, 15.0.1 Patch 2 and earlier and 15.5. The vulnerability could be exploited to allow an XML Exte...
CVE-2021-25323
PUBLISHED: 2021-01-19
The default setting of MISP 2.4.136 did not enable the requirements (aka require_password_confirmation) to provide the previous password when changing a password.
CVE-2021-25324
PUBLISHED: 2021-01-19
MISP 2.4.136 has Stored XSS in the galaxy cluster view via a cluster name to app/View/GalaxyClusters/view.ctp.