by nolovelust
12. April 2011 23:15
Are you using Dropbox to securely store/backup your private files?
Think again! Dropbox can determinate if a file uploaded before by other Dropbox user you can find it out "simply by observing the amount of data transferred between your own computer and Dropbox's servers. If the file isn't already stored by Dropbox, the entire file will be uploaded. If Dropbox has the file already, just a few kb of communication will occur."
"What this means, is that from the comfort of their desks, law enforcement agencies or copyright trolls can upload contraband files to Dropbox, watch the amount of bandwidth consumed, and then obtain a court order if the amount of data transferred is smaller than the size of the file"
Source
by nolovelust
29. January 2011 16:09
Xuxian Jiang recently reported a vulnerability in latest Android version Gingerbread and Nexus S that runs it.
According to article it is poosible to steal information and list of applications from phones sd card and system partitions.
Article does not explain what is the vulnerability but it looks like it is releted to some sort of upload feature. It may be that Android Gingerbread doesn;t request user confirmation for uploads so that you can steal some information by uploading some files via javascript.
Here is the full article:
"While working on an Android-related research project, I came across a data stealing vulnerability in Android 2.3 (Gingerbread). This vulnerability is of the same nature with the one reported by Thomas Cannon during last November on Android 2.2 (Froyo). That particular bug is supposed to be fixed in Android 2.3 (Gingerbread) -- see the links here, here, here, and there.
Unfortunately, our finding here is that the patch contained in Android 2.3 is not an ultimate fix and can still be bypassed. We have a proof-of-concept exploit with a stock Nexus S phone and are able to successfully exploit the vulnerability to steal potentially personal information from the phone. The attack works by requiring the user to visit a malicious link. Based on the experiments with one of our Nexus S phones, we have leveraged the vulnerability to
Obtain the list of applications that are currently installed in the phone;
Upload the applications (located in /system and /sdcard partitions) to a remote server;
Read and upload the contents of any file (including photos, saved voicemails...) stored on the phone's /sdcard. Note that to do that, the exact pathname/filename needs to be known.
I notified the Google Android Security Team on 01/26/2011 and was pleased/impressed to receive their response within 10 minutes. After that, we exchanged emails, including a critical piece of exploit code, to better understand the nature of the vulnerability. From the interaction, I can tell that they took this issue seriously and the investigation was started immediately without any delay. Also, I need to mention that this attack is not a root exploit, meaning it still runs within the Android sandbox and cannot grab all files on the system (only those on the /sdcard and a limited number of others).
The vulnerability is now confirmed and I was told that an ultimate fix will be included no later than the next major release of Android. We are not aware of any active exploitation of this issue.
For responsible disclosure, I will not publish the details of the vulnerability until an ultimate fix is out. However, I would like to share the common intention by informing users about the potential risk (and absolutely NOT about how to exploit), which is the reason why I created this webpage.
Before the ultimate fix is out, there are several ways we can take to mitigate this threat. For example, we can temporarily disable Javascript support in the Android browser or switch to a third-party browser for the time being (e.g., Firefox). We can also choose to unmount the /sdcard. But that may greatly affect the usability of the phone. Users are also encouraged to be cautious when viewing unfamiliar websites.
Finally, I'd like to thank Nick from the Android Security Team for verifying the presence of this vulnerability and keeping me informed as this fix progresses."