CVE-2017-7162
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 11.2 is affected. macOS before 10.13.2 is affected. tvOS before 11.2 is affected. watchOS before 4.2 is affected. The issue involves the "IOKit" 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 confidenceMemory corruption vulnerability in IOKit allows a malicious app to execute arbitrary code in a privileged context or cause a denial of service. The vulnerability affects iOS before 11.2, macOS before 10.13.2, tvOS before 11.2, and watchOS before 4.2.
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< 11.2< 10.13.2< 11.2< 4.2CVSS 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.
-
Identify your Apple operating systemCheck which Apple device you have: iPhone (iOS), Mac (macOS), Apple TV (tvOS), or Apple Watch (watchOS). This determines which version range applies.Affected if The device runs any of the affected Apple operating systems listed.
-
Determine the installed iOS versionOn iPhone, go to Settings > General > About and note the Version number. Compare this to the affected range: versions before 11.2 are vulnerable.Affected if iOS version is lower than 11.2 (for example, 11.1.x, 11.0.x, or earlier).
-
Determine the installed macOS versionOn Mac, click the Apple menu > About This Mac. The version number is displayed (for example, 10.13.1, 10.13.0). Compare to the affected range: versions before 10.13.2 are vulnerable.Affected if macOS version is lower than 10.13.2 (for example, 10.13.1, 10.13.0, or earlier).
-
Determine the installed tvOS versionOn Apple TV, go to Settings > General > About. Note the version number. Compare to the affected range: versions before 11.2 are vulnerable.Affected if tvOS version is lower than 11.2.
-
Determine the installed watchOS versionOn Apple Watch, open the Watch app on your paired iPhone, go to General > About. Note the version. Compare to the affected range: versions before 4.2 are vulnerable.Affected if watchOS version is lower than 4.2.
Your environment is affected if the installed OS version is below the specified threshold (iOS 11.2, macOS 10.13.2, tvOS 11.2, or watchOS 4.2) for your Apple device.
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 data4.210.13.211.2
Apply vendor-supplied patches by updating to iOS 11.2+, macOS 10.13.2+, tvOS 11.2+, or watchOS 4.2+ as appropriate for the affected system.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7162 — 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-7162 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