You have to wonder when will companies learn that securing customer data isn’t optional. I say that because Kromtech Security Center which is the parent company of MacKeeper Security has found that thousands of FedEx customers have had their private information exposed after one of the courier’s Amazon S3 servers was left open without a password. FedEx got the server as part of buying a company called Bongo International a few years ago. Now here’s the really bad part, after Kromtech reached out to FedEx to tell them about the security screw up, the server was then yanked from pubic view. Which implies that they had no clue that this server was sitting out there wide open for anyone to find.
So, what data are we talking about here? Nothing significant really. Just passport information, driver’s licenses and other high profile security info that would allow any miscreant to steal your identity. And the data comes from customers around the world.
Ouch.
Bob Diachenko, head of communications, Kromtech Security Center had this to say:
“Technically, anybody who used Bongo International services back in 2009-2012 is at risk of having his/her documents scanned and available online for so many years. Seems like bucket has been available for public access for many years in a row. Applications are dated within 2009-2012 range, and it is unknown whether FedEx was aware of that “heritage” when it bought Bongo International back in 2014″
For it’s part, FedEx had this to say:
“After a preliminary investigation, we can confirm that some archived Bongo International account information located on a server hosted by a third-party, public cloud provider is secure. The data was part of a service that was discontinued after our acquisition of Bongo. We have found no indication that any information has been misappropriated and will continue our investigation.”
Seeing as this S3 server was available for who knows how long, nobody knows if data was swiped. If I were FedEx, I’d assume that data was swiped by the forces of evil and then start reaching out to those who had info on this server and give them the heads up. Because these days you can’t be too careful.
A Nasty Bug Is Discovered In macOS High Sierra Related To APFS Disk Images
Posted in Commentary with tags Apple on February 16, 2018 by itnerdThe quality issues with Apple software keep popping up. Last night I became aware of a new one that while it would be a bit of an edge case, is still pretty serious. Mike Bombich of Bombich Software who make the popular Carbon Copy Cloner backup software discovered a pretty bad bug when it comes to disk images formatted for Apple’s shiny new APFS file system. Before I get to the bug, let me explain what disk images are.
In short, disk images are basically files that behave like hard disks. You can store thousands of files in them and mount and unmount them like hard disks. In other words, it’s a pretty cool way to back up stuff as it’s a pretty easy concept to understand for most users. Disk images on the Mac platform have been around forever and even Apple uses them with its Time Machine backup application. Thus, you might have used a disk image and not even been aware of it.
Now here’s the bug as described by Bombich:
Earlier this week I noticed that an APFS-formatted sparsebundle disk image volume showed ample free space, despite that the underlying disk was completely full. Curious, I copied a video file to the disk image volume to see what would happen. The whole file copied without error! I opened the file, verified that the video played back start to finish, checksummed the file – as far as I could tell, the file was intact and whole on the disk image. When I unmounted and remounted the disk image, however, the video was corrupted. If you’ve ever lost data, you know the kick-in-the-gut feeling that would have ensued. Thankfully, I was just running some tests and the file that disappeared was just test data. Taking a closer look, I discovered two bugs in macOS’s “diskimages-helper” service that lead to this result.
Well, that’s a #fail and a pretty bad one. He then tested on disk images formatted for HFS+ which is Apple’s previous file system and didn’t get this result. Thus he believes that this was an oversight rather than a regression (a regression is something that started out working fine and then broke at some point). More on that in a moment. But because this was a serious enough bug, he took the step of putting out an update to Carbon Copy Cloner that stops users from using APFS formatted disk images as well as filing a bug report with Apple. He also recommends that nobody on planet Earth use APFS formatted disk images until this issue is addressed.
This is clearly a QA fail as I would expect that a test case would have been built around testing an APFS formatted disk image to see if it had the same functionality of an HFS+ disk image. Clearly that didn’t happen here and it underlines the issues that Apple clearly has with the quality of their software. Now earlier this week I tweeted out a story from Bloomberg about a how Apple will address these systemic issues:
Hopefully that yields results as the current state of affairs is not that good.
Leave a comment »