SafariWeb browser · Apple
CVE-2017-7022
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 execute arbitrary code in a privileged context or cause a denial of service (memory corruption) 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 confidenceCVE-2017-7022 is a kernel-level vulnerability in Apple iOS, macOS, tvOS, and watchOS that allows a maliciously crafted application to execute arbitrary code with kernel privileges or cause memory corruption leading to denial of service. The flaw exists in the Kernel component and enables privilege escalation from a local application context.
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
SafariWeb browser
<= 10.1.1<= 10.3.2<= 10.2.1<= 6.2.1<= 12.6.1CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check iOS version on iPhone/iPadGo to Settings > General > About > Version, or connect device to computer and check in iTunes/ Finder device summaryAffected if Version is 10.3.2 or earlier
-
Check macOS versionClick Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if Version is 10.12.5 or earlier (kernel-level flaw requires macOS 10.12.6 or later to be fixed)
-
Check tvOS version on Apple TVGo to Settings > General > About > VersionAffected if Version is 10.2.1 or earlier
-
Check Safari version on macOSOpen Safari > About Safari, or check Application folder versionAffected if Safari version is 10.1.1 or earlier (note: the underlying kernel flaw may also exist in older macOS versions)
-
Verify kernel extension loading capabilityOn macOS, check System Preferences > Security & Privacy > General for 'Allow apps downloaded from' settings. On iOS, any installed app can attempt exploitationAffected if Device runs any third-party applications (the vulnerability is exploitable by a maliciously crafted local application)
You are affected if any Apple device (iPhone, iPad, Mac, Apple TV) runs an OS version at or below the affected ranges listed (iOS 10.3.2, macOS 10.12.5, tvOS 10.2.1, Safari 10.1.1) and has third-party applications installed.
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 dataApply vendor-provided security updates: iOS 10.3.3 or later, macOS 10.12.6 or later, tvOS 10.2.2 or later, and watchOS 3.2.3 or later. Organizations should inventory affected devices, test updates in controlled environments, and deploy patches systematically.
Fix this in Safari
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7022 — 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-7022 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