Operations

6/5/2016
08:00 AM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

How Risky Is Bleeding Edge Tech?

Experts with the Carnegie Mellon University Software Engineering Institute rate 10 up-and-coming technologies for risk.
Previous
1 of 11
Next

Image Source: Adobe Stock

Image Source: Adobe Stock

Most seasoned information security experts know that when a new technology starts taking off like wildfire, chances are pretty good that someone's going to get burned. The curve of innovation for decades has generally traversed a path where engineers think of features, bells and whistles first, security last.

As a new crop of exciting technology like smart medical devices, drones and driverless cars jockeys for position in the mainstream, the question is how much risk they'll bring to the table. A panel of experts with the Carnegie Mellon University Software Engineering Institute recently took a look at some of the hottest tech making its way to the forefront to answer this very question. Here are some of the highlights from the report, 2016 Emerging Technology Domains Risk Survey.

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
6/6/2016 | 7:45:38 AM
VR
When it came to choosing which VR headset I would buy earlier this year, I went over and over in my head with all the different pros and cons.

While the Vive seemed like the Superior headset, I was worried about HTC's potential financial difficulties. 

Admittedly in the end I got both and will now sell my Rift on, but I do still wonder how quickly VR is going to catch on. I think it might take a couple of years, at which point the Vive will be oudated, but by then hopefully we'll be looking at second generation devices.
12 Free, Ready-to-Use Security Tools
Steve Zurier, Freelance Writer,  10/12/2018
Most IT Security Pros Want to Change Jobs
Dark Reading Staff 10/12/2018
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.