Yikes! iOS 13 Coming Next Week With iPhone LockScreen Bypass Bug

Sep 13, 2019

Good news… next week, on September 19, Apple will roll out
iOS 13, the latest version of its mobile operating system.

Yes, we’re excited about, but here comes the bad news…

iOS 13 contains a vulnerability that could allow anyone to
bypass the lockscreen protection on your iPhone and access some
sensitive information.

Jose
Rodriguez ^[1], a Spanish security
researcher, contacted The Hacker News and revealed that he
discovered a lockscreen bypass bug in iOS 13 that allowed him to
access the full list of Contacts on his iPhone—and every piece of
information saved on them.

Rodriguez told The Hacker News that he discovered the new
lockscreen bypass bug on his iPhone running iOS 13 beta version and
reported it to Apple on July 17.

However, unfortunately, Apple failed to patch the bug even after
being informed months ago, and the bypass is still working on the
Gold Master (GM) version of iOS 13, the final version of the
software that will be rolled out to everyone on September 19.

How Does iOS 13 Lockscreen Bypass On iPhone Work?

The bug allows anyone with physical access to a target’s iPhone to
trick the smartphone into granting access to the full list of
stored Contacts, as well as detailed information for each
individual contact including their names, phone numbers, and
emails—all using nothing but a FaceTime call.

The latest iPhone lockscreen bypass
hack is similar to the one Rodriguez discovered last year in iOS
12.1, just a few hours after Apple released iOS 12.1, allowing
anyone to bypass the lockscreen on a targeted iPhone using the
built-in VoiceOver feature.
^[2]^[3]

To demonstrate the new iPhone hack, Rodriguez shared a video with
The Hacker News, as shown below, demonstrating how the hack works
and relatively how simple it is to perform by any non-techie user.

The bug involves activating a FaceTime call on a target’s iPhone
and then accessing Siri’s voiceover support feature to obtain
access to the contact list—and every information saved on them.

However, more likely, Apple will patch this issue in the iOS
13.1 release, which is expected to arrive for the public on
September 30. So all users should patch their iPhones by the end of
the month.

Until then iPhone users are recommended to not leave their phone
unattended, at least in public and workplaces.

References

^{^}
Jose Rodriguez
(twitter.com)
^{^}
lockscreen bypass hack
(thehackernews.com)
^{^}
last year in iOS 12.1
(thehackernews.com)

The Hacker News Headlines

Google Chrome’s New Feature Alerts Users About Auto-Removal of Malicious Extensions

Aug 18, 2023

The Hacker News Headlines

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

Aug 18, 2023

The Hacker News Headlines

China-Linked Bronze Starlight Group Targeting Gambling Sector with Cobalt Strike Beacons

Aug 18, 2023

OWASP TOP !0

Injection. Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization. Broken Authentication. Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently. Sensitive Data Exposure. Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser. XML External Entities (XXE). Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks. Broken Access Control. Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc. Security Misconfiguration. Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely fashion. Cross-Site Scripting XSS. XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites. Insecure Deserialization. Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks. Using Components with Known Vulnerabilities. Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts. Insufficient Logging & Monitoring. Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.

Yikes! iOS 13 Coming Next Week With iPhone LockScreen Bypass Bug

How Does iOS 13 Lockscreen Bypass On iPhone Work?

References

Related Post

Google Chrome’s New Feature Alerts Users About Auto-Removal of Malicious Extensions

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

China-Linked Bronze Starlight Group Targeting Gambling Sector with Cobalt Strike Beacons

You missed

Protected: Rotary VI EAST

Protected: BetterCyberCareer Group

Protected: Benin Club 1931 – Official

Protected: Whatsapp AI Automation Group