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
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
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
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?


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-1809
PUBLISHED: 2022-05-21
Access of Uninitialized Pointer in GitHub repository radareorg/radare2 prior to 5.7.0.
CVE-2022-31267
PUBLISHED: 2022-05-21
Gitblit 1.9.2 allows privilege escalation via the Config User Service: a control character can be placed in a profile data field, such as an emailAddress%3Atext '[email protected]\n\trole = "#admin"' value.
CVE-2022-31268
PUBLISHED: 2022-05-21
A Path Traversal vulnerability in Gitblit 1.9.3 can lead to reading website files via /resources//../ (e.g., followed by a WEB-INF or META-INF pathname).
CVE-2022-31264
PUBLISHED: 2022-05-21
Solana solana_rbpf before 0.2.29 has an addition integer overflow via invalid ELF program headers. elf.rs has a panic via a malformed eBPF program.
CVE-2022-31259
PUBLISHED: 2022-05-21
The route lookup process in beego through 1.12.4 and 2.x through 2.0.2 allows attackers to bypass access control. When a /p1/p2/:name route is configured, attackers can access it by appending .xml in various places (e.g., p1.xml instead of p1).