Apple iOS/iPadOS up to 14.1 IOAcceleratorFamily memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Apple iOS and iPadOS up to 14.1. It has been classified as critical. The affected element is an unknown function of the component IOAcceleratorFamily. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2020-27905. The attack must be initiated from a local position. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in Apple iOS and iPadOS up to 14.1 (Smartphone Operating System). This affects an unknown code block of the component IOAcceleratorFamily. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was shared 11/05/2020 by Mohamed Ghannam as HT211929 as confirmed advisory (Website). It is possible to read the advisory at support.apple.com. This vulnerability is uniquely identified as CVE-2020-27905. The exploitability is told to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/06/2020). It is expected to see the exploit prices for this product increasing in the near future. The advisory points out:
A malicious application may be able to execute arbitrary code with system privileges
Upgrading to version 14.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
A memory corruption issue was addressed with improved state management.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: iOS/iPadOS 14.2
Timeline
10/27/2020 🔍11/05/2020 🔍
11/05/2020 🔍
11/06/2020 🔍
12/02/2020 🔍
Sources
Vendor: apple.comAdvisory: HT211929
Researcher: Mohamed Ghannam
Status: Confirmed
CVE: CVE-2020-27905 (🔍)
GCVE (CVE): GCVE-0-2020-27905
GCVE (VulDB): GCVE-100-164379
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 11/06/2020 08:28Updated: 12/02/2020 20:04
Changes: 11/06/2020 08:28 (18), 11/06/2020 08:32 (29), 12/02/2020 20:04 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.