Cloud

2/16/2018
11:00 AM
50%
50%

FedEx Customer Data Exposed on Unsecured S3 Server

Thousands of documents from US and international citizens were exposed on an Amazon S3 bucket configured for public access.

Data belonging to thousands of global FedEx customers was exposed on an unsecured Amazon Simple Storage Service (S3) server configured for public access, Kromtech security analysts discovered earlier this month.

The exposed bucket belonged to Bongo International LLC, a company created to help North American companies market to customers around the world. FedEx acquired Bongo in 2014. Two years later, it relaunched it as FedEx Cross-Border International, which shut down in 2017.

Although the organization was closed, data inherited from 2009-2012 remained available on the server, exposing personal identifiable information from citizens representing Canada, Japan, China, Australia, the EU, and other countries until the bucket was removed from public access this month. The server contained more than 119,000 scanned documents including passports, driver's licenses, and security IDs, in addition to scanned "Applications for Delivery of Mail Through Agent" forms with names, home addresses, phone numbers, and zip codes.

FedEx reports it has no evidence the data was compromised but is still investigating the matter. The company joins a growing list of organizations that have unintentionally compromised consumer data by failing to properly secure their Amazon S3 storage buckets -- a trend that continues as more businesses move to the cloud without taking proper security precautions.

"We need to get our heads out of the clouds, because cloud services are only as secure as you make them," says Brian NeSmith, CEO and cofounder at Arctic Wolf Networks. "Companies need to start applying the same rigor and discipline to their cloud infrastructure as they do to their on premises network."

On top of that, a recently discovered search engine makes it easier to look for data left on misconfigured S3 servers. The service, dubbed BuckHacker, lets people search by file name or bucket name, which may include the name of the business using the server.

Read more details on the FedEx leak here.

 

 

 Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

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
2/18/2018 | 4:18:17 PM
FedEx Customer Data Exposed
While this story might seem almost trivial (as the technical vulnerability is known, with no signs of immediate impact); I'd call it a "must read" - carefully! 

It is the very innocuousness of the described data breach that is most troubling; as the attitudes and events that lead to it are pandemic in kind.  

"Although the organization was closed, data inherited from 2009-2012 remained available on the server..."  Where have you heard something like that before?  If you've been listening - everywhere.  You wouldn't even have to hear it to expect it, if you appreciate the way data is bought, sold, traded, stolen, abandoned, recycled, repurposed, relocated, disseminated, reconstituted....

There's another troubling element in the article: "On top of that, a recently discovered search engine makes it easier to look for data left on misconfigured S3 servers."  Bad news for anyone who left S3 buckets unattended, and for those unknowing potential victims of poor data governance; but the news gets worse - as the idea of specialized search engines will become bad news for other discovered-vulnerable data storage schemes going forward. 
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-20031
PUBLISHED: 2019-03-21
A Denial of Service vulnerability related to preemptive item deletion in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor ...
CVE-2018-20032
PUBLISHED: 2019-03-21
A Denial of Service vulnerability related to message decoding in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor daemon t...
CVE-2018-20034
PUBLISHED: 2019-03-21
A Denial of Service vulnerability related to adding an item to a list in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor ...
CVE-2019-3855
PUBLISHED: 2019-03-21
An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.
CVE-2019-3858
PUBLISHED: 2019-03-21
An out of bounds read flaw was discovered in libssh2 before 1.8.1 when a specially crafted SFTP packet is received from the server. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.