Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

New iOS Keylogging Vulnerability Discovered 72

exomondo writes "Following hot on the heels of the iOS (and OS X) SSL security bug comes the latest vulnerability in Apple's mobile operating system. It is a security bug that can be used as a vector for malware to capture touch screen, volume rocker, home button and (on supported devices) TouchID sensor presses, information that could be sent to a remote server to re-create the user's actions. The vulnerability exists in even the most recent versions of iOS and the authors claim that they delivered a proof-of-concept monitoring app through the App Store."
This discussion has been archived. No new comments can be posted.

New iOS Keylogging Vulnerability Discovered

Comments Filter:
  • by bazmail ( 764941 ) on Tuesday February 25, 2014 @01:38PM (#46336983)
    apple software has "bugs".
    • At least Microsoft is conducting research to reduce bugs.
      See for example: http://research.microsoft.com/... [microsoft.com]

      Not sure where Apple stands.

    • Re: (Score:2, Interesting)

      by alen ( 225700 )

      this one relies on apps that run in the background and "listen" to touch inputs

      since android is multitasking as well i assume it has the same issues

      • Re: (Score:2, Interesting)

        by Anonymous Coward

        Background tasks don't receive touch input. That's why they are in the background.

        Unless you are iOS and have this vulnerability.

      • by rehtonAesoohC ( 954490 ) on Tuesday February 25, 2014 @02:21PM (#46337551) Journal
        You can't assume that because android also has multi-tasking that it also has a security vulnerability... It's a completely different system with completely different designs. That's like saying that because an apple has skin that you should also eat people too.
    • by tero ( 39203 )

      You didn't even read the summary? That's very /. of you

      " iOS (and OS X) SSL security bug comes the latest vulnerability in Apple's mobile operating system"

      • by bazmail ( 764941 )
        I tried to be all-inclusive and use the lowest form of wit as the basis for a joke, but it seems to have passed clear over your head.
        I will try to include pie-in-the-face gags and poop in my next humor-based post.

        NO SLASHDOTTER LEFT BEHIND!!!!
      • Hehe you missed a fairly thick joke there :)

        No one is denying that another vulnerability was found. Vulnerabilities will be found in any software.

    • apple software has "bugs".

      It's a glitch.

    • And if they allow privilege escalation they're called "jailbreaks".

    • Any complex software has bugs and perfection is never available. The important question remains: how are the users treated? If the software respects a user's freedoms to run, inspect, share, and modify the software [gnu.org], users are treated well. If these freedoms are not respected, the user is subjugated. This is an ethical issue with technical ramifications.

      Non-free programs (such as Microsoft Windows and Apple's OSes) are designed and licensed to prohibit anyone but the proprietor from understanding how the sof

    • I shouldn't need to be explaining this on Slashdot, but the two are not necessarily the same, and one is not a polite euphemism for the other. A bug may lead to a vulnerability, or it may not, since it could be as benign as unexpected output for the provided input or as dangerous as the stuff we hear about here each day.

      In contrast, vulnerabilities are always dangerous, though to varying extents, and they may not always be caused by software bugs (though I suppose there is an argument to be made that you ca

  • Goes to show... (Score:5, Insightful)

    by jones_supa ( 887896 ) on Tuesday February 25, 2014 @01:43PM (#46337053)
    As Apple products keep gaining larger market share, also the number of discovered vulnerabilities increases day after day. Having a UNIX base does not mean that you are automatically invincible.
    • by Anonymous Coward

      gaining a larger market share?

      they are going backwards.....

      the only place that buys apple products in a large quantity is the US....

      9% market share..... yep everyone is buy them

  • by Ronin Developer ( 67677 ) on Tuesday February 25, 2014 @02:12PM (#46337421)

    The method of how the app was installed on a non-jail broken device was not discussed. While I would say that being able to capture touches and such by an background app is a potential threat, getting the software on a device is easier said than done.

    Mobile Management Systems (MMS) have access to APIs that can also do these sorts of things.

    I would venture that this was one using either developer mode or as an enterprise app and not through the the AppStore. Jailbroken devices are, clearly, more at risk.

    Now...a bigger question. Can the same be done on Android devices? I am betting "Yes"????

     

    • Now...a bigger question. Can the same be done on Android devices? I am betting "Yes"????

      I'd be willing to bet that it can as well.

      So what does that mean? iOS is just as vulnerable as Android?

      • iOS is just as vulnerable as Android?

        Not quite. It just means that iOS isn't as invulnerable as many claim.

  • 35 messages on this thread as I read it, and only ONE says in any detail anything that shows the issue and what the vulnerability has as an underlying assumption. Here it is for those who did read the article (RTFA), you have to install a rogue app. So, someone who's breaking the ToS (not being rogue) has to put an app out, then you have to install it, and then it's scraping inputs. This isn't a security vulnerability as most responses on here opine about. My car has a gas pedal. Does the ECM for engine management have a "security vulnerability," because I can press hard on the right pedal and do 180mph (illegal by federal law)?? No. It's functioning as designed. Press hard on gas, go faster. App installed and running in background, can accept device inputs. For example, have a GPS app? It is allowing inputs from other applications (e.g. you can listen to music on the GPS app I have without kicking out to Music app) and inputs (buttons).

    Nothing significant to see here. Yeah, more restrictions from Apple development guidelines coming due to asshats being asshats. *sigh*

    • Re: (Score:2, Interesting)

      by Anonymous Coward

      So, someone who's breaking the ToS (not being rogue) has to put an app out, then you have to install it, and then it's scraping inputs.

      Oh so it's not a security vulnerability if it's against the Terms of Service, wow Microsoft should implement a ToS and then most of their Windows security issues will cease to exist.

      This isn't a security vulnerability as most responses on here opine about.

      Of course it is, how do you figure that a process running in the background being able to break out of the sandbox restrictions and capture all inputs is not a security vulnerability? You would have to be a complete Apple shill to be in such denial about a bug like this.

      My car has a gas pedal. Does the ECM for engine management have a "security vulnerability," because I can press hard on the right pedal and do 180mph (illegal by federal law)?? No. It's functioning as designed.

      Yet the application sandboxing in iOS is clearly not workin

    • by Anonymous Coward

      you have to install a rogue app.

      That is how most malware works, unless you have a privilege escalation bug. And iOS has had at least one such web-based drive-by bug (jailbreakme.com) so there are probably more undiscovered ones.

      So, someone who's breaking the ToS

      I can't imagine people looking to infect devices with keylogging malware are living in fear of the terms of service.

      This isn't a security vulnerability as most responses on here opine about.

      Of course it is. Background processes capturing touch

    • by AmiMoJo ( 196126 ) *

      You entirely missed the point. There is no "log all keyboard input" permission for apps to request. I don't think the TOS are very likely to prevent a black hat deploying the exploit. Since Apple doesn't examine every line of code in apps they approve they now need to either close the hole or develop a tool to detect when compiled code tries to make use of it.

      I expect a few apps will be getting updates to remove this exploit now, before Apple closes it off and notices them crashing.

  • 01. Download malware .. 02. Install malware ... 03. Get infected ....
    • 04. Wipe hands on pants.
    • The real danger here is the ability for the system to automatically update apps to the latest version, which has been a feature since the release of iOS 7. The threat comes from when a developer of an existing app sells it to another company intent on updating that app to include this piece of malware. Suddenly, that little-known game you play every day is a trojan just waiting to infect you the next time you play it. So while the steps that you outlined are still the same, the change here is that steps 1 a

      • by Smerta ( 1855348 )
        Yes, but isn't that under the user's control? The iOS user decides if apps auto-update or not, correct?
        • by Sancho ( 17056 )

          You can opt-out, certainly. How many will? How many will not just hit the "update all" button if they do opt out?

  • There have always been holes in the App Store and sometimes you can sneak things through.

    The difference is if you try such things and you app becomes even remotely popular, Apple can pull your app and even your developer account so the actual window where your fraud or evil tricks can result in some kind of gain is very small.

    I'm not sure why people constantly fail to recognize this.

    Similarly with the SSL flaw... Apple pushes iOS updates in a way Android users can only dream of; within a month more than 90%

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (10) Sorry, but that's too useful.

Working...