Apple iOS up to 6.1.4 Personal Hotspot credentials management

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.
6.2$5k-$25k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Apple iOS up to 6.1.4. Affected by this issue is some unknown functionality of the component Personal Hotspot. Performing a manipulation results in credentials management. This vulnerability is identified as CVE-2013-4616. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Apple iOS up to 6.1.4 (Smartphone Operating System). This affects some unknown functionality of the component Personal Hotspot. The manipulation with an unknown input leads to a credentials management vulnerability. CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:

The WifiPasswordController generateDefaultPassword method in Preferences in Apple iOS 6 and earlier relies on the UITextChecker suggestWordInLanguage method for selection of Wi-Fi hotspot WPA2 PSK passphrases, which makes it easier for remote attackers to obtain access via a brute-force attack that leverages the insufficient number of possible passphrases.

The weakness was released 09/18/2013 by Andreas Kurtz and Daniel Metz as APPLE-SA-2013-09-18-2 iOS 7 as confirmed mailinglist post (Website). The advisory is shared at prod.lists.apple.com. The mailinglist post contains:

An issue existed in the generation of Personal Hotspot passwords, resulting in passwords that could be predicted by an attacker to join a user's Personal Hotspot. The issue was addressed by generating passwords with higher entropy.
This vulnerability is uniquely identified as CVE-2013-4616 since 06/18/2013. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/25/2021). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1552 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 69984 (Apple iOS < 7 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Mobile Devices.

Upgrading to version iOS 7.0 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (85111), Tenable (69984), SecurityFocus (BID 60616†), Secunia (SA54886†) and Vulnerability Center (SBV-42756†). Further details are available at zdnet.com. Entries connected to this vulnerability are available at VDB-5610, VDB-8303, VDB-8792 and VDB-8797. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Credentials management
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 69984
Nessus Name: Apple iOS < 7 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍
Upgrade: iOS iOS 7.0

Timelineinfo

06/17/2013 🔍
06/17/2013 +0 days 🔍
06/18/2013 +1 days 🔍
06/18/2013 +0 days 🔍
09/18/2013 +92 days 🔍
09/18/2013 +0 days 🔍
09/19/2013 +0 days 🔍
09/20/2013 +1 days 🔍
01/01/2014 +103 days 🔍
05/25/2021 +2701 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: APPLE-SA-2013-09-18-2 iOS 7
Researcher: Andreas Kurtz, Daniel Metz
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2013-4616 (🔍)
GCVE (CVE): GCVE-0-2013-4616
GCVE (VulDB): GCVE-100-10341
X-Force: 85111
SecurityFocus: 60616
Secunia: 54886 - Apple iOS Multiple Vulnerabilities, Highly Critical
SecurityTracker: 1029054
Vulnerability Center: 42756 - Apple iOS <7 Remote Security Bypass Vulnerability via Personal Hotspot, Medium

scip Labs: https://www.scip.ch/en/?labs.20150917
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 09/20/2013 10:34
Updated: 05/25/2021 10:11
Changes: 09/20/2013 10:34 (74), 05/18/2017 17:44 (1), 05/25/2021 10:02 (3), 05/25/2021 10:06 (2), 05/25/2021 10:11 (2)
Complete: 🔍
Cache ID: 216:1BF:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!