CVE-2017-7115 json
An issue was discovered in certain Apple products.
published 2017-10-23 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16153
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.7%
- EPSS 7.7% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered in certain Apple products. iOS before 11 is affected. tvOS before 11 is affected. The issue involves the "Wi-Fi" component. It might allow remote attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via crafted Wi-Fi traffic that leverages a race condition.
Timeline
- First public exploit (EDB-42996)
- Published
Exploit prediction
7.67% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-42996 Apple iOS 10.2 (14C92) - Remote Code Execution remote, 2017-10-17
- bugs.chromium.org https://bugs.chromium.org/p/project-zero/issues/detail?id=1317 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
exploit-db.com
/exploits/42996/
exploit, third-party-advisory, vdb-entry
-
bugs.chromium.org
/p/project-zero/issues/detail?id=1317
exploit, issue-tracking, mitigation, technical-description, third-party-advisory
-
support.apple.com
/HT208113
vendor-advisory
-
support.apple.com
/HT208112
vendor-advisory
-
securityfocus.com
/bid/100924
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1039385
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-7115
- NVD CVE-2017-7115
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.