If you’re a customer of US retail chain Staples, you may have recently received a notification from the company regarding a problem with their Order Tracking system.

According to information in the notification, the data was left exposed due to insufficient protections of the data stream accessed when a customer clicked to review their current and past orders.

The company stressed that to this point, there is no evidence that any exposed data has been accessed by third parties and no unauthorized purchases have been detected.

Although the company has now fixed the issue, the lack of specifics in the company notification led to speculation that the company may have been hacked. This speculation was given teeth by a recent tweet from the threat intelligence company, Bad Packets. They revealed that Staples was slow to patch a number of their Pulse Secure VPN servers, which were vulnerable to CVE-2019-11510.

Although the company has neither confirmed or denied the claim made by Bad Packets, the company outlined an all too plausible way that a hacker could have accessed order data, including the order’s shipping address.

Here’s how that could have happened:

Staples’ order tracking portal allows you to enter in your zip code and order number to track your package, but the order numbers are sequential. So starting with an exposed order number, a hacker could access the route of a package to the city and state, which would give them a short list of possible zip codes. Trial and error would do the rest, and the hacker would end up with your name, address, and at least some information about how you paid for the purchase, although payment card information itself would not have been exposed.

In any case, it’s all speculation and the issue has been fixed. Out of an abundance of caution, if you are a Staples customer, keep a watchful eye out on the payment card you use to make purchases from the company, and track your existing orders more closely to be sure you get everything you paid for.

Used with permission from Article Aggregator

error: Alert: Content is protected !!