Apple iOS/iPadOS up to 15.1.1 IOMobileFrameBuffer out-of-bounds write

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical has been found in Apple iOS and iPadOS up to 15.1.1. This vulnerability affects unknown code of the component IOMobileFrameBuffer. Performing a manipulation results in out-of-bounds write. This vulnerability is known as CVE-2021-30985. Attacking locally is a requirement. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Apple iOS and iPadOS up to 15.1.1 (Smartphone Operating System). It has been classified as critical. This affects some unknown processing of the component IOMobileFrameBuffer. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 12/13/2021 by Tielei Wang as HT212976 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2021-30985. 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 03/08/2026). 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 kernel privileges
Upgrading to version 15.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
An out-of-bounds write issue was addressed with improved bounds checking.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2022-0489). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Apple iPad
- Apple iPhone
- Apple iOS
- Apple iPadOS
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: Out-of-bounds writeCWE: CWE-787 / 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 15.2
Timeline
04/13/2021 🔍12/13/2021 🔍
12/13/2021 🔍
12/17/2021 🔍
03/08/2026 🔍
Sources
Vendor: apple.comAdvisory: HT212976
Researcher: Tielei Wang
Status: Confirmed
CVE: CVE-2021-30985 (🔍)
GCVE (CVE): GCVE-0-2021-30985
GCVE (VulDB): GCVE-100-188565
CERT Bund: WID-SEC-2022-0489 - Apple iOS: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 12/17/2021 16:42Updated: 03/08/2026 14:31
Changes: 12/17/2021 16:42 (1), 12/17/2021 16:43 (18), 12/17/2021 16:46 (28), 12/23/2021 09:38 (1), 03/08/2026 14:31 (20)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.