Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Thursday April 23 2015, @07:45PM   Printer-friendly
from the maybe-if-you-hold-it-differently dept.

The Guardian is reporting on a newly discovered bug in IOS which causes iDevices to continually crash and reboot.

Once the user has entered what its discoverer, security researchers Skycure, dubs the “no iOS Zone”, there’s no way to fix their phone other than escaping the range of the malicious network; every time it reboots, it crashes almost immediately.

The basis of the attack uses a “specially crafted SSL certificate”, typically used to ensure a secure connection, to trigger a bug in the operating system that crashes out any app using SSL.

More info on Skycure's blog.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Interesting) by Tork on Thursday April 23 2015, @09:29PM

    by Tork (3914) Subscriber Badge on Thursday April 23 2015, @09:29PM (#174445)
    Right, but what happens if you try to connect to a no-password SSID by whilst a password? I'll put it another way: Let's say I create a hotspot called Tork, you connect to it, and you have to enter (and save) a password to authenticate to it. Then, after you've used it for a while, I go to my router and remove the password and set up the hack mentioned in the article. Would an iPhone connect to Tork and start rebooting or would it fail to authenticate because the handshake is all gibberish?
    --
    🏳️‍🌈 Proud Ally 🏳️‍🌈
    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 0) by Anonymous Coward on Thursday April 23 2015, @09:42PM

    by Anonymous Coward on Thursday April 23 2015, @09:42PM (#174449)

    What I think he is suggesting is to pro-actively enter "bad data" for your carrier specific SSID (so that the phone will fail to connect to it and be immune to the attack.) My guess is the carrier SSID is already hard-coded, but it might be worth a try to see if it's even possible.