Skip to main content

Sign in with Apple vulnerability allowed unauthorised access to linked accounts

Apple’s “Sign in with Apple”  was found to have a vulnerability that would allow hackers to gain access to any account that was linked with the service. The vulnerability was discovered by Bhavuk Jain, an Indian security researcher who promptly reported to Apple. Apple investigated the matter, Apple did conclude the vulnerability to be real and awarded the researcher a sum of $10,000 as part of the bug-bounty program.

The vulnerability in question was around how Apple validated users “on the client-side before initiating a request from Apple’s authentication services.” A JSON Web token would be generated by the server which would be used by the third-party service to authenticate the user. The vulnerability would allow this token to be spoofed, leading to any malicious actor to gain access to a user’s account. "I found I could request JWTs for any Email ID from Apple, and when the signature of these tokens was verified using Apple's public key, they showed as valid. This means an attacker could forge a JWT by linking any Email ID and gaining access to the victim's account," Jain said in an Interview with The Hacker News. The vulnerability would impact even those users who chose to hide or not share their email IDs during the login process.

Apple had introduced Sign in With Apple last year at WWDC as a means of providing iOS users an alternative to having to use their Facebook or Google IDs to log into third-party applications. The need arose from the fact that Facebook and Google were leveraging these sign-in for advertising purposes and even going so far as to tracking user behaviour. Facebook was even accused of selling user data to third parties, and then there was the Cambridge Analytica scandal. Twitter too was accused of selling user data to the people behind Cambridge Analytica. Apple’s pitch with Sign in with Apple was that the service wouldn’t collect or track user behaviour. In fact, Apple even built an email anonymizer into the service, where users could opt to not share their e-mail IDs with the platform they were logging into. In the backend, Apple would create a bridge email ID which would forward any correspondence from the platform to the users’ actual email ID. Sign in with Apple would generate unique e-mail IDs for every service you sign into, provided you choose to not share your email ID with that service.

Apple has stated that the vulnerability in question has been patched by the company and that after verifying their server logs, say that no accounts were accessed illegitimately.



from Latest Technology News https://ift.tt/3eDEpIe

Comments

Popular posts from this blog

Apple Seeds iOS 18.5 Developer Beta 3 Update for iPhone; Public Beta 2 Also Released

Apple on Monday rolled out the iOS 18.5 Developer Beta 3 update to developers and beta testers. It arrives as a minor update for the iPhone with similar features in tow. Alongside, it bundles fixes for a bug that caused black screen to appear on the new Apple Vision Pro. Apple also seeded the iOS 18.5 Public Beta 2 update with a handful of changes compared to the publ... from Gadgets 360 https://ift.tt/ZGYOJvf

What if a botched Google search card says you are a serial killer

Many of us have come to heavily rely on Google Search and often don’t question the veracity of information Google cherry-picks from the vast data available on the world wide web for its search cards. This incident, which is one part funny and two parts scary, makes it clear that Google’s Knowlege Graph may not be as sacrosanct as you may have believed.  Hristo Georgiev was informed by a former colleague that a Google search of his name returned a Google Knowlege Graph that depicted his photo and linked it to a Bulgarian rapist and serial killer of the same name, also known as ‘The Sadist’, who murdered five people back in the 1970s and was later executed by shooting.  The graph linked the info to a Wikipedia article, which incidentally had no link to any of Georgiev’s profile or his image. It was Google’s algorithms that erroneously matched the two. What’s even more problematic is that Hristo Georgiev is not a unique name and is shared by hundreds of other people.  As...