Endpoint

5/22/2018
11:45 AM
50%
50%

Pet Tracker Flaws Expose Pets and Their Owners to Cybercrime

Hackers can exploit vulnerabilities in popular pet trackers to intercept location coordinates and access owners' personal data.

In a future where everything is connected, cybercriminals may not need to target you to steal your personal data. They can hack your pets instead. 

Kaspersky Lab researchers today published the results of a study investigating vulnerabilities in popular pet trackers, which transfer GPS coordinates from pets to owners for safety and location monitoring. The flaws they discovered could let an attacker hack these devices, identify and replace the coordinates of a pet and its owner, and access owners' data.

In studying several brands of pet trackers, researchers found: Bluetooth capabilities that don't require authentication, authorization tokens and coordinates that can be stored sans encryption, trackers that don’t check server certificates for HTTPS connections, and trackers and apps that allow the installation of false firmware and transmit the name, email, and coordinates of the pet's owner.

It's another reason to worry about the implications of poor IoT security. If a hacker can intercept these coordinates, they can identify where a pet or owner is at any given time, learn their daily routines, and over time develop a pattern of owners' and animals' habits.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
5/22/2018 | 1:11:44 PM
If you use the internet to track something, so can anyone else - no news here
Your kids, your pets, your workouts... whatever; with breaches in even high security environments commonplace, why do people feel they have a justifiable expectation of security with their consumer devices and services?  I think we all know the answers: marketing which downplays or totally ignores security concerns (or overstates included security features), for IoT devices and services; to be followed by marketing of devices and services to secure your IoT. 
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/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-15504
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. The server mishandles some HTTP request fields associated with time, which results in a NULL pointer dereference, as demonstrated by If-Modified-Since or If-Unmodified-Since with a month greater than 11.
CVE-2018-15505
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. An HTTP POST request with a specially crafted "Host" header field may cause a NULL pointer dereference and thus cause a denial of service, as demonstrated by the lack of a trailing ']' character in an IPv6 a...
CVE-2018-15492
PUBLISHED: 2018-08-18
A vulnerability in the lservnt.exe component of Sentinel License Manager version 8.5.3.35 (fixed in 8.5.3.2403) causes UDP amplification.
CVE-2018-15494
PUBLISHED: 2018-08-18
In Dojo Toolkit before 1.14, there is unescaped string injection in dojox/Grid/DataGrid.
CVE-2018-15495
PUBLISHED: 2018-08-18
/filemanager/upload.php in Responsive FileManager before 9.13.3 allows Directory Traversal and SSRF because the url parameter is used directly in a curl_exec call, as demonstrated by a file:///etc/passwd value.