Apple iOS 10/10.1 on iPad2 Lockscreen improper authentication

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Apple iOS 10/10.1 on iPad2. It has been classified as problematic. This vulnerability affects unknown code of the component Lockscreen. This manipulation causes improper authentication. The attack can only be executed locally. Furthermore, there is an exploit available. It is recommended to apply the suggested workaround.

Detailsinfo

A vulnerability was found in Apple iOS 10/10.1 on iPad2 (Smartphone Operating System). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component Lockscreen. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was shared 11/17/2016 by Benjamin Kunz Mejri as VL-ID 2012 / 648680301 as confirmed advisory (Website). It is possible to read the advisory at vulnerability-lab.com. The vendor was not involved in the public release. The exploitation appears to be difficult. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The advisory points out:

The vulnerability is located after installtion of the ios 10.x version to the incompatible apple ipad2 device. The website of the apple site showed us that imcompatible devices can cause on usage in unexpected behavoir, so we decided to install the version to one of our test environment devices. After the installation we have noticed that the dictionary function became available ahead to the desk. In our testings we used the function to trigger a glitch on accessing the more information button in the locked device mode. After processing the interaction manually in a loop, we was able to get ahead the passcode screen area a push magnifying glass preview.

A public exploit has been developed by Benjamin Kunz Mejri and been published immediately after the advisory. It is possible to download the exploit at vulnerability-lab.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The advisory illustrates:

Watching the bug displayed information of a restricted area that is located in `Device - Siri - About Sir & Data Security to Privacy`. Now i moved to the link by searching blind the location and pushed twice to receive the input menu bar like when marking a text. People that are aware of ios know that these function allows several options depending on the input and connected function. Now an attacker can use the share function that became visible ahead during the passcode lock screen via glitch and pushs the share button. Now the email opens. Then the attacker marks the email of the contact and pushs twice the contact plus a keyboard letter of an exisiting contact. Now the contact comes ahead, click the info button and move to the profil location. Add the information to a new contact, then press the image button and now the attacker is able to access the photo album of the device without any restrictions.

The best possible mitigation is suggested to be Workaround.

Additional details are provided at seclists.org. The entries VDB-93680, VDB-93681 and VDB-93682 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

Video

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.9
VulDB Meta Temp Score: 4.5

VulDB Base Score: 4.9
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper authentication
CWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Benjamin Kunz Mejri
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Workaround
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Timelineinfo

11/17/2016 🔍
11/17/2016 +0 days 🔍
11/19/2016 +2 days 🔍
07/25/2019 +978 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: VL-ID 2012 / 648680301
Researcher: Benjamin Kunz Mejri
Status: Confirmed

GCVE (VulDB): GCVE-100-93679
scip Labs: https://www.scip.ch/en/?labs.20150917
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 11/19/2016 17:33
Updated: 07/25/2019 06:26
Changes: 11/19/2016 17:33 (54), 07/25/2019 06:26 (2)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!