CVE-2017-6975 json
Wi-Fi in Apple iOS before 10.3.1 does not prevent CVE-2017-6956 stack buffer overflow exploitation via a crafted access point.
published 2017-04-05 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16013
- cvss
- 6.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
Wi-Fi in Apple iOS before 10.3.1 does not prevent CVE-2017-6956 stack buffer overflow exploitation via a crafted access point. NOTE: because an operating system could potentially isolate itself from CVE-2017-6956 exploitation without patching Broadcom firmware functions, there is a separate CVE ID for the operating-system behavior.
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- googleprojectzero.blogspot.com https://googleprojectzero.blogspot.com/2017/04/over-air-exploiting-broadcoms-wi-fi_4.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.8 | CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
googleprojectzero.blogspot.com
/2017/04/over-air-exploiting-broadcoms-wi-fi_4.html
exploit, technical-description, third-party-advisory
-
support.apple.com
/HT207688
vendor-advisory
-
securitytracker.com
/id/1038172
vdb-entry
-
securityfocus.com
/bid/97328
vdb-entry, third-party-advisory
-
twitter.com
/4Dgifts/status/849268365457850370
third-party-advisory
-
seclists.org
/fulldisclosure/2019/May/24
mailing-list
- support.apple.com /kb/HT210121
-
seclists.org
/bugtraq/2019/May/30
mailing-list
Sources
- CVE List CVE-2017-6975
- NVD CVE-2017-6975
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.