Comments
Connected Cars Pose New Security Challenges
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/8/2018 | 2:11:05 PM
Long history
Alas, automakers have a history of downplaying (and even ignoring) exploits and vulnerabilities in their cars (see, e.g., forbes.com/forbes/welcome/?toURL=https://www.forbes.com/sites/andygreenberg/2013/07/24/hackers-reveal-nasty-new-car-attacks-with-me-behind-the-wheel-video/ ). Can't say as I particularly trust them.
Jon M. Kelley
50%
50%
Jon M. Kelley,
User Rank: Strategist
3/8/2018 | 11:38:24 AM
Re: Connected cars need extensive blackbox testing
Once Mobile Ransomware starts hitting connected cars, the U.S. government may get involved as it did with seatbelts and airbags.  Given history we may have decades of connected cars before government regulations force manufacturers to fix them.  Unfortunately for consumers, manufacturers have learned that remote software updates are very cost effective.  This will leave the connection available for others, as well as manufacturers, to try to turn it into a revenue stream. 
HamidK95001
50%
50%
HamidK95001,
User Rank: Author
3/6/2018 | 3:41:28 PM
Connected cars need extensive blackbox testing
A rapidly emerging trend is to apply extensive blackbox testing for connected cars and in particular fuzzing seems to be rather effctive in exposing hidden weaknesses. 


Meet 'Bro': The Best-Kept Secret of Network Security
Greg Bell, CEO, Corelight,  6/14/2018
Four Faces of Fraud: Identity, 'Fake' Identity, Ransomware & Digital
David Shefter, Chief Technology Officer at Ziften Technologies,  6/14/2018
Containerized Apps: An 8-Point Security Checklist
Jai Vijayan, Freelance writer,  6/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-5236
PUBLISHED: 2018-06-20
Symantec Endpoint Protection prior to 14 RU1 MP1 or 12.1 RU6 MP10 may be susceptible to a race condition (or race hazard). This type of issue occurs in software where the output is dependent on the sequence or timing of other uncontrollable events.
CVE-2018-5237
PUBLISHED: 2018-06-20
Symantec Endpoint Protection prior to 14 RU1 MP1 or 12.1 RU6 MP10 could be susceptible to a privilege escalation vulnerability, which is a type of issue that allows a user to gain elevated access to resources that are normally protected at lower access levels.
CVE-2018-6211
PUBLISHED: 2018-06-20
On D-Link DIR-620 devices with a certain customized (by ISP) variant of firmware 1.0.3, 1.0.37, 1.3.1, 1.3.3, 1.3.7, 1.4.0, and 2.0.22, OS command injection is possible as a result of incorrect processing of the res_buf parameter to index.cgi.
CVE-2018-6212
PUBLISHED: 2018-06-20
On D-Link DIR-620 devices with a certain customized (by ISP) variant of firmware 1.0.3, 1.0.37, 1.3.1, 1.3.3, 1.3.7, 1.4.0, and 2.0.22, a reflected Cross-Site Scripting (XSS) attack is possible as a result of missed filtration for special characters in the "Search" field and incorrect proc...
CVE-2018-6213
PUBLISHED: 2018-06-20
In the web server on D-Link DIR-620 devices with a certain customized (by ISP) variant of firmware 1.0.3, 1.0.37, 1.3.1, 1.3.3, 1.3.7, 1.4.0, and 2.0.22, there is a hardcoded password of anonymous for the admin account.