111–120 of 186 posts
Earlier quoted context omitted.
The special feature of these "pseudo USSD" codes on Android is that you don't have to press the call button. Simply typing the digits is enough. Note I have no idea if this particular attack actually works.
I don't think it's "android feautre", I've seen this on a few non-smart phones in the past. I don't know which one though as I owned few of them over the years.
I'd been using the app Hidden Menus (https://play.google.com/store/apps/details?id=com.lorenx.and...) which stopped working at the ICS -> JB transition. You now need to type USSD/star codes manually.
Perhaps this puts a new face on the Android OS update/fragmentation problem.
I'm 95% sure this bug was fixed between ICS and Jelly Bean. I'd been using the app Hidden Menus ( https://play.google.com/store/apps/details?id=com.lorenx.and... ) which stopped working at the ICS -> JB transition. You now need to type USSD/star codes manually. Perhaps this puts a new face on the Android OS update/fragmentation problem.
Earlier quoted context omitted.
My local bus company has failed to grasp QR codes in a mind-bogglingly thorough way. Every stop has a poster with a QR code on it, advertising that you can now look up when the next bus will be here by scanning the QR code. The first thing you might notice is that the poster is actually a photo of a QR code on a poster, and is taken at an angle sufficient to render scanning the QR code impossible. The second thing yo…
Maybe they got the idea from Google Code, which helpfully shows me a QR code for the tarball I'm about to download, for all those times I'm using the browser on my desktop and the IDE on my phone.
Here's a safe version of the exploit that displays your IMEI: http://kristofferR.com/samsung.html Check the html in your desktop browser first, for all you know I might as well be a malicious douchebag. The exploit seems to require a stock Samsung Galaxy dialer, works fine on my cheap Samsung Galaxy Y but not on my friend's modded S3 with a vanilla Android dialer.
Can anyone confirm that this is not only a safe USSD, but that it triggers the exploit? I am not an owner of a S3, but would love to be able to help show some of my non-tech friends whether they are vulnerable to this or not
After investigating further, the S3 does not launch codes that begin with * # but will trigger the factory reset code which is in the format of * 1234 * 1234 #
Edit: Those with an S3 can confirm this by visiting http://no.tl/s.html in which I've embedded * 1234 * 1234 # (which is not the reset code, but is the same format)
Here's a safe version of the exploit that displays your IMEI: http://kristofferR.com/samsung.html Check the html in your desktop browser first, for all you know I might as well be a malicious douchebag. The exploit seems to require a stock Samsung Galaxy dialer, works fine on my cheap Samsung Galaxy Y but not on my friend's modded S3 with a vanilla Android dialer.
I'm 95% sure this bug was fixed between ICS and Jelly Bean. I'd been using the app Hidden Menus ( https://play.google.com/store/apps/details?id=com.lorenx.and... ) which stopped working at the ICS -> JB transition. You now need to type USSD/star codes manually. Perhaps this puts a new face on the Android OS update/fragmentation problem.
Here's a safe version of the exploit that displays your IMEI: http://kristofferR.com/samsung.html Check the html in your desktop browser first, for all you know I might as well be a malicious douchebag. The exploit seems to require a stock Samsung Galaxy dialer, works fine on my cheap Samsung Galaxy Y but not on my friend's modded S3 with a vanilla Android dialer.
Earlier quoted context omitted.
If you want to check the functionality - it would be far more responsible to use a non-destructive USSD code. e.g. *#06# displays the phone's IMEI number
Testing this myself, any USSD code that begins with * # launches the device's dialler with no characters dialled. Looking at the list of codes: http://umitem.blogspot.com.au/2010/10/samsung-galaxy-s-i9000... The factory reset appears to be the only USSD "auto dialled" code that doesn't begin with *#. Which is rather unfortunate. Edit: Actually, the IMEI code works on the Galaxy S2 running 2.3 (just tested) but not th…
Earlier quoted context omitted.
Testing this myself, any USSD code that begins with * # launches the device's dialler with no characters dialled. Looking at the list of codes: http://umitem.blogspot.com.au/2010/10/samsung-galaxy-s-i9000... The factory reset appears to be the only USSD "auto dialled" code that doesn't begin with *#. Which is rather unfortunate. Edit: Actually, the IMEI code works on the Galaxy S2 running 2.3 (just tested) but not th…
You need to replace # with %23