CVE-2017-7029
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in certain Apple products. iOS before 10.3.3 is affected. macOS before 10.12.6 is affected. tvOS before 10.2.2 is affected. watchOS before 3.2.3 is affected. The issue involves the "Kernel" component. It allows attackers to bypass intended memory-read restrictions via a crafted app.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceKernel memory-read restriction bypass vulnerability in Apple iOS, macOS, tvOS, and watchOS that allows a locally-running malicious application to read protected kernel memory that should be restricted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.3.3< 10.12.6< 10.2.2< 3.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple device typeDetermine whether the device runs iOS (iPhone/iPad), macOS (Mac computer), tvOS (Apple TV), or watchOS (Apple Watch). This determines which version threshold applies.Affected if Device runs any of the affected Apple operating systems.
-
Check iOS version on iPhone or iPadOpen Settings > General > About > Version. Note the version number displayed (for example, 10.3.2). Alternatively, connect the device to a computer with iTunes and view the device summary page.Affected if Version is below 10.3.3 (for example, 10.3.2, 10.3.1, 10.2.x, etc.).
-
Check macOS version on MacClick the Apple menu in the top-left corner and select 'About This Mac'. The version number appears in the window that opens (for example, 10.12.5). Alternatively, open Terminal and run: sw_vers -productVersionAffected if Version is below 10.12.6 (for example, 10.12.5, 10.12.4, 10.11.x, etc.).
-
Check tvOS version on Apple TVGo to Settings > General > About > Version. Note the version number displayed (for example, 10.2.1).Affected if Version is below 10.2.2 (for example, 10.2.1, 10.2.0, 10.1.x, etc.).
-
Check watchOS version on Apple WatchOn Apple Watch: go to Settings > General > About > Software Version. Or on the paired iPhone: open the Watch app, go to General > About > watchOS Version.Affected if Version is below 3.2.3 (for example, 3.2.2, 3.2.1, 3.1.x, etc.).
If the detected OS version falls below 10.3.3 on iOS, 10.12.6 on macOS, 10.2.2 on tvOS, or 3.2.3 on watchOS, the device is vulnerable to this kernel memory-read restriction bypass.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.2.310.2.210.3.3
Apply vendor-supplied OS updates: iOS 10.3.3+, macOS 10.12.6+, tvOS 10.2.2+, and watchOS 3.2.3+ to patch the kernel vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-7029 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data