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
SCOTUS Says Suit Over Fiat-Chrysler Hack Can Move Forward
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/16/2019 | 9:38:30 AM
Re: Might have is not the basis for lawsuit
Thats not really what I was positing. My assertion that other individuals will fall under this category of owning a vulnerable Jeep. If they fall under the use case and it is determined that Fiat-Chrysler does have to pay out then they may be able to collect utilizing that lawsuit as a citation. It happens all the time from a medical perspective. "If you've been exposed to x, then you could be entitled to appropriations." Law offices advertise from this angle quite a bit. So not sure why its such a ludicrous assertion when it happens quite often.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
1/14/2019 | 3:21:56 PM
Might have is not the basis for lawsuit
Gee, I worked on the 101st floor of the south tower and had I known that one day in September it would be lowered from 101 to the ground floor level, I might have chosen a different job, so WHO can i sue over a decision I MIGHT have made.  Lawsuits don't work that way.  Ever.  And it gets into Minority report territory.  What I am arrested for something I MIGHT have done or MIGHT do.  Well there is some social media in that one but even so suing a company for something that might have influenced a purchase decision?????  HEY, WHAT ABOUT VOLKSWAGEN???   Lets take them down too, lousy Germans!!!
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/14/2019 | 2:37:36 PM
Scope of Lawsuit
What is the reach of this lawsuit? By this I mean, if it turns out that Fiat-Chrysler needs to pay the accusers, could other vulnerable Jeep users jump on the band wagon and file ancillary lawsuits if the company still refuses to patch?


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.