Got a tip for us? Share it...

Safari Autofill Security Issue Permits Access to Personal Information


Earlier this week, The Register detailed a security vulnerability found in Apple's Safari Autofill feature that could enable malicious websites to extract users' personal information from their Address Book entries. The security researcher, Jeremiah Grossman of WhiteHat Security, followed up with a blog post yesterday detailing the exploit and offering a proof of concept webpage allowing users to see if they are vulnerable.

The vulnerability arises from Address Book's usage of simple form text fields to store the user's personal information, paired with Safari's ability to automatically grab that information through its Autofill feature to assist users with filling out web forms.

All a malicious website would have to do to surreptitiously extract Address Book card data from Safari is dynamically create form text fields with the aforementioned names, probably invisibly, and then simulate A-Z keystroke events using JavaScript. When data is populated, that is AutoFill'ed, it can be accessed and sent to the attacker.

For some reason, fields that begin with numbers such as phone numbers and street addresses are not subject to this vulnerability. A user's name, company affiliation, city/state/country, and email addresses can, however, typically be accessed.

Still, such attacks could be easily and cheaply distributed on a mass scale using an advertising network where likely no one would ever notice because it's not exploit code designed to deliver rootkit payload. In fact, there is no guarantee this has not already taken place. What is safe to say is that this vulnerability is so brain dead simple that I assumed someone else must have publicly reported it already, but exhaustive searches and asking several colleagues turned up nothing.

Grossman reports that he submitted information on the vulnerability to Apple on June 17th, but has received nothing more than an automatic acknowledgement of his submission despite an attempted follow-up. Consequently, Grossman is making public disclosure of the vulnerability so that users can take steps to protect themselves by disabling the Autofill feature, which is turned on by default.

Update: According to All Things Digital, Apple has acknowledged the issue and promised that it is working on a fix, but no timeframe for a release has been shared.

Top Rated Comments

(View all)

20 months ago
Another reason not to use autofill.
Rating: 0 Positives / 0 Negatives
20 months ago
Rating: 0 Positives / 0 Negatives
20 months ago
Dammit, I like autofill.
Rating: 0 Positives / 0 Negatives
20 months ago
This can be scary. It's surprising no-one has made a big deal about this until now.
Rating: 0 Positives / 0 Negatives
20 months ago
Self inflicted spam! Ha
Rating: 0 Positives / 0 Negatives
20 months ago
+1 on not using auto fill.

Why are there so many security vulnerabilities showing up all at once for :apple:?
Rating: 0 Positives / 0 Negatives
20 months ago

http://arstechnica.com/security/news/2010/07/apple-the-new-world-leader-in-software-insecurity.ars


Though this does not necessarily mean that Apple's software is the most insecure in practice—the report takes no consideration of the severity of the flaws—it points at a growing trend in the world of security flaws: the role of third-party software. Many of Apple's flaws are not in its operating system, Mac OS X, but rather in software like Safari, QuickTime, and iTunes. Vendors like Adobe (with Flash and Adobe Reader) and Oracle (with Java) are similarly responsible for many of the flaws being reported.
Rating: 0 Positives / 0 Negatives
20 months ago

+1 on not using auto fill.

Why are there so many security vulnerabilities showing up all at once for :apple:?


Safari. Just use Firefox and you are safer than Windows and almost as safe as Linux.
Rating: 0 Positives / 0 Negatives
20 months ago
What about passwords autofill? I have that option on.
Rating: 0 Positives / 0 Negatives
20 months ago
Rating: 0 Positives / 0 Negatives

[ Read All Comments ]