| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Apple watchOS up to 3.1.0. It has been classified as critical. This vulnerability affects unknown code of the component Accounts. This manipulation causes improper authorization. This vulnerability is handled as CVE-2016-7651. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical was found in Apple watchOS up to 3.1.0 (Smartwatch Operating System). Affected by this vulnerability is an unknown code block of the component Accounts. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 12/13/2016. The weakness was released 12/12/2016 with Trend Micro as HT207426 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is known as CVE-2016-7651 since 09/09/2016. An attack has to be approached locally. The requirement for exploitation is a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue. The advisory points out:
This issue was addressed through improved sanitization.
Upgrading to version 3.1.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94851†). Entries connected to this vulnerability are available at VDB-94138, VDB-94131, VDB-94142 and VDB-94143. 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: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: Improper authorizationCWE: CWE-285 / CWE-266
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: watchOS 3.1.1
Timeline
09/09/2016 🔍12/12/2016 🔍
12/12/2016 🔍
12/12/2016 🔍
12/13/2016 🔍
12/13/2016 🔍
02/20/2017 🔍
10/05/2022 🔍
Sources
Vendor: apple.comAdvisory: HT207426
Organization: Trend Micro
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-7651 (🔍)
GCVE (CVE): GCVE-0-2016-7651
GCVE (VulDB): GCVE-100-94141
SecurityFocus: 94851 - Apple iOS and watchOS CVE-2016-7651 Security Bypass Vulnerability
SecurityTracker: 1037429
See also: 🔍
Entry
Created: 12/13/2016 19:44Updated: 10/05/2022 23:32
Changes: 12/13/2016 19:44 (62), 06/25/2019 09:22 (8), 10/05/2022 23:32 (4)
Complete: 🔍
Cache ID: 216:D88: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.