| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Apple iOS up to 10.3.0 and classified as critical. This affects an unknown part of the component Wi-Fi. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2017-6975. It is feasible to perform the attack on the physical device. No exploit exists. The affected component should be upgraded.
Details
A vulnerability was found in Apple iOS up to 10.3.0 (Smartphone Operating System). It has been declared as critical. Affected by this vulnerability is an unknown part of the component Wi-Fi. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 04/03/2017. The weakness was disclosed 04/03/2017 by Gal Beniamini with Google Project Zero as HT207688 as confirmed advisory (Website). The advisory is shared at support.apple.com. The public release has been coordinated in cooperation with Apple. This vulnerability is known as CVE-2017-6975 since 03/17/2017. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The advisory points out:
An attacker within range may be able to execute arbitrary code on the Wi-Fi chip
Upgrading to version 10.3.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 97328†) and SecurityTracker (ID 1038172†). Additional details are provided at seclists.org. The entry VDB-134969 is pretty similar. 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: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: Yes
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 10.3.1
Timeline
03/17/2017 🔍04/03/2017 🔍
04/03/2017 🔍
04/03/2017 🔍
04/03/2017 🔍
04/04/2017 🔍
04/04/2017 🔍
04/05/2017 🔍
11/27/2022 🔍
Sources
Vendor: apple.comAdvisory: HT207688
Researcher: Gal Beniamini
Organization: Google Project Zero
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2017-6975 (🔍)
GCVE (CVE): GCVE-0-2017-6975
GCVE (VulDB): GCVE-100-99277
SecurityFocus: 97328 - Apple iOS CVE-2017-6975 Arbitray Code Execution Vulnerability
SecurityTracker: 1038172
scip Labs: https://www.scip.ch/en/?labs.20150917
Misc.: 🔍
See also: 🔍
Entry
Created: 04/04/2017 11:18Updated: 11/27/2022 07:02
Changes: 04/04/2017 11:18 (77), 10/25/2019 20:49 (3), 11/27/2022 07:02 (4)
Complete: 🔍
Cache ID: 216:6BE: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.