The international transportation company, Uber, has announced they have fixed the software glitch that exposed hundreds of its driver’s personal information.
Many of Ubers United States drivers took to forums like Reddit to complain about the incident, stating they were able to view sensitive documents like social security numbers, driver’s licenses, vehicle registration information, and tax forms.
Uber has come out and stated that this flaw has affected 674 of its US drivers and exposed less than 1,000 documents in total. The glitch allowed logged-in drivers who visited the documents page to view the details of other Uber drivers.
Although Uber was able to fix the flaw within thirty minutes, drivers are worried that their exposed credentials could be used by drivers to commit identity fraud.
In a statement from Uber:
“We were notified about a bug impacting a fraction of our US drivers earlier this afternoon. Within 30 minutes out security team had fixed the issue. We’d like to thank the driver who drew it to our attention and apologize to those drivers whose information may have been affected. Their security is incredibly important to Uber and we will follow up with them directly.”
Luckily Uber was able to mend this issue in a very short period of time, but not all breaches are dealt with as swiftly. It’s vitally important that regardless of company size, that each organization make it a priority to have a defense strategy planned in case something like this should arise. Not only will you be able to make your employees and customers feel at ease, but you’ll also be able to minimize any financial or legal risk that could arise.
Also, implementing best in class security solutions like File Integrity Monitoring, Change & Configuration Management, Device Hardening, Breach Detection and Continuous Compliance can help your organization mitigate these risks. Breaches will always happen, but having the right tools in place to help minimize these risks will help alleviate the consequences.
Read more on Change Tracker Gen7
Read the full article on InfoSecurity Magazine