Bug In iOS, OS X Allows AirDrop To Write Files Anywhere On File System
Trailrunner7 writes: There is a major vulnerability in a library in iOS and OS X that allows an attacker to overwrite arbitrary files on a target device and, when used in conjunction with other techniques, install a signed app that the device will trust without prompting the user with a warning dialog. Mark Dowd, the security researcher who discovered it, said he's been able to exploit the flaw over AirDrop, the feature in OS X and iOS that enables users to send files directly to other devices. If a user has AirDrop set to allow connections from anyone—not just her contacts—an attacker could exploit the vulnerability on a default locked iOS device. In fact, an attacker can exploit the vulnerability even if the victim doesn't agree to accept the file sent over AirDrop.
Of course the bug is worrisome, but then, I consider the setting that allows it—leaving AirDrop open to everyone—to be a pretty ridiculous personal security flaw. Making one’s phone readily available to connections from random sources for the sole purpose of file drops doesn’t sound like something that should make the least bit of sense to even the average user.
Use it or lose it.
That's because Windows has complex security holes that require a lot of hacking. With this flaw, Apple clearly shows that hacking "just works" on their devices.
... The NSA want to steal your data, not fill your drive up with software signed by Apple that can be traced directly back to a well documented person that apple has communicated with financially on more than one occasion.
You don't even know what this does, so just STFU
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
If a user has AirDrop set to allow connections from anyone—not just her contacts—an attacker could exploit the vulnerability on a default locked iOS device.
What the fuck is wrong with using the word "their"?
Although...
Mark Dowd, the security researcher who discovered it, said he's been able to exploit the flaw over AirDrop, the feature in OS X and iOS that enables users to send files directly to other devices.
Perhaps Mark Dowd is female. If so then... Hmm. Then... I dunno.
Either way, there are a whole group of words that are not gender specific. Use them(!), and stop with this retarded "her" crap.
Thanks.
Yeah, I was surprised by this article. I can hardly ever get it to write files anywhere -- even where it's supposed to.
Check to see whether it's disabled already, open a command prompt and run:
defaults read com.apple.NetworkBrowser | grep DisableAirDrop
If it returns DisableAirDrop = 1, then you should be fine. If it comes up blank, or if it shows DisableAirDrop = 0, then AirDrop is not disabled by default. In this case, run:
defaults write com.apple.NetworkBrowser DisableAirDrop -bool YES
You'll need to log out and log back in for the change to take effect.
references: this Apple Forums thread
Finding God in a Dog
It does not matter if you have switched off airdrop or restricted its access to known contacts.
At a border crossing an officer can take your locked device and push some nasty payload to it.
Even a confirmation would be useless as it would be another guy pressing okay.
...a kernel issue, rather than an issue w/ iOS or OS-X? Wouldn't they have to look at XNU and debug that?
That sounds like a really weak attempt to come to the rescue of your favorite corporate brand.
If it's a fundemental design bug, then it's still a bug.
A Pirate and a Puritan look the same on a balance sheet.
"If a user has AirDrop set to allow connections from anyone..."
Ok, so you have a setup where people can push files at you, and if you allow anybody to do it, someone might drop a malicious file in your system? What about the fact that Apple allows you to leave your laptop unattended and unlocked, say, on the subway? A malicious person could take over your whole computer! That's a serious vulnerability, and proves that Macs are no safer than Windows machines.
-- sudon't
Air-ride Equipped
who even knows AirDrop is a thing in OS X?
NOW who's engaging in Selection Bias?
IIRC, AirDrop was available for OS X BEFORE it came out for iOS.
Yep. AirDrop was available on OS X 10.7 (Lion), released on July 10, 2011, but not available on iOS until iOS 7, some two years later.
Way to keep up with technology, 'tard!
It's a bug, not yet another NSA/GCHQ backdoor that offers Apple "deniability" of their collusion with intelligence agencies.
Citation, please!
Obviously the numbers of IOS devices makes them a better target now
Wait! I thought that Android was the big gorilla, and iOS was at 14% and shrinking fast.
So which is it?
You are just saying anything to make yourself sound intelligent. Which you obviously are not; since you can't even use an APOSTROPHE correctly. It's POSSESIVE, not PLURALIZATION, FUCKTARD!
Oh, and you might consider using a COMMA once in awhile, too.
Goto fail.
No reasonable explanation. Patching error? Fuck off.
Spoken by someone who has never written a line of code, nor screwed up a cut and paste operation.
Why not patch the current version? Especially for devices that are not covered by iOS9.
Is there a single device which is supported on 8.4 that isn't supported on 9?
Correct me if I'm wrong, but, unlike Android's obsoleting devices every revision or two, I don't believe any device was obsoleted by IOS 9.
You're a fucking NSA/Apple shill. Did you look into it at all?
LOL!!! You have NO idea how far both of those allegations are from the truth!
Yes I have looked into it.
The Internet is like the Bible: There are so many conflicting opinions, that you can prove ANY position. One site thinks that it is clear indication of purposeful sabotage; the next thinks that it is a cut and paste error; and the third site isn't sure, but says it's Apple, so it HAS to be evil.
My honest opinion, if I had to guess, and as a person who has coded professionally for about four decades, was that someone intended to remove an "IF..." Statement (now deleted) on the line just above the second "goto fail" line, and simply failed to remove the "goto fail". I've actually made that mistake myself, more than once. Not often, but it does happen. Combine that with a little "testing bias", and there is absolutely a very real chance that this was an honest coding mistake.