Apple watchOS up to 5.3.8/6.2.8/7.0.3 libxml2 integer overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Apple watchOS up to 5.3.8/6.2.8/7.0.3. This impacts an unknown function of the component libxml2. Such manipulation leads to integer overflow. This vulnerability is documented as CVE-2020-27911. The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Apple watchOS up to 5.3.8/6.2.8/7.0.3 (Smartwatch Operating System) and classified as critical. Affected by this issue is an unknown part of the component libxml2. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability.
The weakness was released 11/05/2020 by OSS-Fuzz as HT211928 as confirmed advisory (Website). The advisory is available at support.apple.com. This vulnerability is handled as CVE-2020-27911. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The advisory points out:
A remote attacker may be able to cause unexpected application termination or arbitrary code execution
Upgrading to version 5.3.9, 6.2.9 or 7.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
An integer overflow was addressed through improved input validation.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 5.3.0
- 5.3.1
- 5.3.2
- 5.3.3
- 5.3.4
- 5.3.5
- 5.3.6
- 5.3.7
- 5.3.8
- 6.2.0
- 6.2.1
- 6.2.2
- 6.2.3
- 6.2.4
- 6.2.5
- 6.2.6
- 6.2.7
- 6.2.8
- 7.0.0
- 7.0.1
- 7.0.2
- 7.0.3
License
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: watchOS 5.3.9/6.2.9/7.1
Timeline
10/27/2020 🔍11/05/2020 🔍
11/05/2020 🔍
11/06/2020 🔍
12/03/2020 🔍
Sources
Vendor: apple.comAdvisory: HT211928
Researcher: OSS-Fuzz
Status: Confirmed
CVE: CVE-2020-27911 (🔍)
GCVE (CVE): GCVE-0-2020-27911
GCVE (VulDB): GCVE-100-164426
Entry
Created: 11/06/2020 09:18Updated: 12/03/2020 08:52
Changes: 11/06/2020 09:18 (19), 11/06/2020 09:21 (27), 12/03/2020 08:52 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.