Apple iOS/iPadOS up to 13.1.3 AVEVideoEncoder memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Apple iOS and iPadOS up to 13.1.3. This issue affects some unknown processing of the component AVEVideoEncoder. The manipulation leads to memory corruption. This vulnerability is listed as CVE-2019-8795. The attack must be carried out locally. In addition, an exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Apple iOS and iPadOS up to 13.1.3 (Smartphone Operating System). This issue affects an unknown code of the component AVEVideoEncoder. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.
The weakness was presented 10/28/2019 as HT210721 as confirmed advisory (Website). The advisory is shared at support.apple.com. The identification of this vulnerability is CVE-2019-8795. An attack has to be approached locally. A simple authentication is needed for exploitation. Technical details are unknown but a public exploit is available. The advisory points out:
A memory corruption issue was addressed with improved memory handling.
A public exploit has been developed by 08Tc3wBB in Objective-C and been published 2 weeks after the advisory. The exploit is available at github.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k.
Upgrading to version 13.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
See VDB-144510, VDB-144528, VDB-144529 and VDB-144530 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 8.3VulDB Meta Temp Score: 7.9
VulDB Base Score: 8.8
VulDB Temp Score: 7.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: 08Tc3wBB
Programming Language: 🔍
Download: 🔍
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: 🔍
Exploit Delay Time: 🔍
Upgrade: iOS/iPadOS 13.2
Timeline
02/18/2019 🔍10/28/2019 🔍
10/28/2019 🔍
10/31/2019 🔍
11/11/2019 🔍
01/31/2024 🔍
Sources
Vendor: apple.comAdvisory: HT210721
Status: Confirmed
CVE: CVE-2019-8795 (🔍)
GCVE (CVE): GCVE-0-2019-8795
GCVE (VulDB): GCVE-100-144533
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/31/2019 07:37Updated: 01/31/2024 08:16
Changes: 10/31/2019 07:37 (45), 11/12/2019 07:30 (22), 01/31/2024 08:16 (8)
Complete: 🔍
Committer: misc
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.