Apple iOS up to 7.1 IOKit Kernel information disclosure

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.7$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Apple iOS up to 7.1. Affected is an unknown function of the component IOKit Kernel. This manipulation causes information disclosure. This vulnerability is registered as CVE-2014-1320. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Apple iOS up to 7.1 (Smartphone Operating System) and classified as problematic. Affected by this vulnerability is an unknown code of the component IOKit Kernel. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

IOKit in Apple iOS before 7.1.1, Apple OS X through 10.9.2, and Apple TV before 6.1.1 places kernel pointers into an object data structure, which makes it easier for local users to bypass the ASLR protection mechanism by reading unspecified attributes of the object.

The weakness was published 04/22/2014 by Ian Beer with Google Project Zero as HT6208 as confirmed advisory (Website) via Zero Day Initiative (ZDI). The advisory is shared at support.apple.com. The public release has been coordinated with Apple. This vulnerability is known as CVE-2014-1320 since 01/08/2014. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue. The advisory points out:

A set of kernel pointers stored in an IOKit object could be retrieved from userland.

The vulnerability scanner Nessus provides a plugin with the ID 73648 (Mac OS X Multiple Vulnerabilities (Security Update 2014-002)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family MacOS X Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 122028 (Apple Mac OS X Security Update 2014-002 Not Installed (HT6207)).

Upgrading to version 7.1.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:

This issue was addressed through removing the pointers from the object.

The vulnerability is also documented in the databases at Tenable (73648), Secunia (SA58140†) and Vulnerability Center (SBV-44207†). Similar entries are available at VDB-10903, VDB-12773, VDB-12772 and VDB-12771. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Apple iPhone 4/5
  • Apple iPod Touch 5
  • iPad 2/3

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.9
VulDB Meta Temp Score: 4.7

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 73648
Nessus Name: Mac OS X Multiple Vulnerabilities (Security Update 2014-002)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: iOS 7.1.1

Timelineinfo

01/08/2014 🔍
04/22/2014 +104 days 🔍
04/22/2014 +0 days 🔍
04/23/2014 +1 days 🔍
04/23/2014 +0 days 🔍
04/23/2014 +0 days 🔍
04/23/2014 +0 days 🔍
06/17/2021 +2612 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT6208
Researcher: Ian Beer
Organization: Google Project Zero
Status: Confirmed
Coordinated: 🔍

CVE: CVE-2014-1320 (🔍)
GCVE (CVE): GCVE-0-2014-1320
GCVE (VulDB): GCVE-100-13045

IAVM: 🔍

Secunia: 58140 - Apple iOS Multiple Vulnerabilities, Highly Critical
Vulnerability Center: 44207 - Apple iOS <7.1.1 for Multiple Devices, Apple TV <6.1.1 and OS X 10.9 - 10.9.2 Local Security Bypass via Reading a Kernel Pointer, Medium

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

Entryinfo

Created: 04/23/2014 16:35
Updated: 06/17/2021 15:00
Changes: 04/23/2014 16:35 (53), 05/26/2017 03:38 (28), 06/17/2021 15:00 (3)
Complete: 🔍
Cache ID: 216:0C2: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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!