| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Apple tvOS up to 11.2.0. It has been rated as critical. This impacts an unknown function of the component HomeKit. This manipulation causes state issue. This vulnerability is registered as CVE-2017-13903. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability classified as critical was found in Apple tvOS up to 11.2.0 (Digital Media Player). Affected by this vulnerability is an unknown function of the component HomeKit. The manipulation with an unknown input leads to a state issue vulnerability. The CWE definition for the vulnerability is CWE-371. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 12/13/2017. The weakness was published 12/13/2017 by Tian Zhang as HT208357 as confirmed ht208357 (Website). The advisory is shared at support.apple.com. The public release has been coordinated with Apple. This vulnerability is known as CVE-2017-13903 since 08/30/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The advisory points out:
A remote attacker may be able to unexpectedly alter application state
Upgrading to version 11.2.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 102182†), SecurityTracker (ID 1040008†) and Vulnerability Center (SBV-79280†). Additional details are provided at lists.apple.com. Similar entry is available at VDB-110821. 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
Video

CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: State issueCWE: CWE-371
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: tvOS 11.2.1
Timeline
08/30/2017 🔍12/13/2017 🔍
12/13/2017 🔍
12/13/2017 🔍
12/13/2017 🔍
12/13/2017 🔍
12/13/2017 🔍
12/14/2017 🔍
12/20/2017 🔍
12/25/2017 🔍
01/27/2021 🔍
Sources
Vendor: apple.comAdvisory: HT208357
Researcher: Tian Zhang
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2017-13903 (🔍)
GCVE (CVE): GCVE-0-2017-13903
GCVE (VulDB): GCVE-100-110845
SecurityFocus: 102182 - Apple iOS and tvOS CVE-2017-13903 Security Bypass Vulnerability
SecurityTracker: 1040008
Vulnerability Center: 79280 - Apple iOS <11.2.1 Remote Unspecified Vulnerability in HomeKit - CVE-2017-13903, Medium
Misc.: 🔍
See also: 🔍
Entry
Created: 12/20/2017 09:50Updated: 01/27/2021 14:47
Changes: 12/20/2017 09:50 (75), 12/16/2019 10:28 (7), 01/27/2021 14:47 (2)
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.