Iphone OsOperating system · Apple

CVE-2017-7062

CRITICAL · 9.8 CVSS v3.0 Published 2017-07-20
Fix available
A fix is available. Upgrade to after 10.12.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An 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 "Contacts" component. A buffer overflow allows remote attackers to execute arbitrary code or cause a denial of service (application crash).

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 confidence

A buffer overflow vulnerability in the Contacts component of Apple iOS, macOS, tvOS, and watchOS allows remote attackers to execute arbitrary code or cause a denial of service by triggering the overflow through maliciously crafted contact data.

MitigationApply vendor-supplied security updates: iOS 10.3.3, macOS 10.12.6, tvOS 10.2.2, and watchOS 3.2.3 or later. Organizations should inventory all affected devices and deploy patches according to their change management procedures.

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
Iphone OsOperating system
Affected:<= 10.3.2
Mac Os XOperating system
Affected:<= 10.12.5
TvosOperating system
Affected:<= 10.2.1
WatchosOperating system
Affected:<= 3.2.2

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Apple platform
    Determine whether the device runs iOS, macOS, tvOS, or watchOS. For iOS/tvOS, go to Settings > General > About. For macOS, go to System Preferences > About This Mac. For watchOS, use the Watch app on paired iPhone > General > About.
    Affected if Device runs any of the affected platforms (iOS, macOS, tvOS, or watchOS)
  2. Check iOS version
    On iOS device, go to Settings > General > About and note the Version number (for example, 10.3.2).
    Affected if Version is 10.3.2 or lower
  3. Check macOS version
    On Mac, go to System Preferences > About This Mac and note the Version number (for example, 10.12.5).
    Affected if Version is 10.12.5 or lower
  4. Check tvOS version
    On Apple TV, go to Settings > General > About > Version and note the build number.
    Affected if Version is 10.2.1 or lower
  5. Check watchOS version
    On paired iPhone, open Watch app > My Watch > General > About and note the watchOS version.
    Affected if Version is 3.2.2 or lower
  6. Verify Contacts usage
    Confirm the Contacts app is enabled and synced on the device. On iOS, check Settings > Contacts > Accounts. On macOS, open Contacts app and verify accounts are configured.
    Affected if Contacts feature is enabled and the OS version falls within the affected ranges

A user is affected if their device runs iOS 10.3.2 or earlier, macOS 10.12.5 or earlier, tvOS 10.2.1 or earlier, or watchOS 3.2.2 or earlier AND they have the Contacts feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 10.12.5
Interim mitigation

Apply vendor-supplied security updates: iOS 10.3.3, macOS 10.12.6, tvOS 10.2.2, and watchOS 3.2.3 or later. Organizations should inventory all affected devices and deploy patches according to their change management procedures.

Recommended fix High confidence

iOS 10.3.3, macOS 10.12.6, tvOS 10.2.2, watchOS 3.2.3

  1. For iOS devices: Go to Settings > General > Software Update and install iOS 10.3.3 or later
  2. For Mac computers: Go to Apple menu > System Preferences > Software Update and install macOS 10.12.6 (Sierra) or later
  3. For Apple TV: Go to Settings > System > Software Updates and install tvOS 10.2.2 or later
  4. For Apple Watch: Pair with iPhone, open Watch app, go to General > Software Update and install watchOS 3.2.3 or later
  5. After updating, verify the update was successful by checking the OS version in Settings/About

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7062 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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