CVE-2016-7662
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.2 is affected. macOS before 10.12.2 is affected. watchOS before 3.1.3 is affected. The issue involves the "Security" component, which allows remote attackers to spoof certificates via unspecified vectors.
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 · moderate confidenceThis is a certificate spoofing vulnerability in Apple's Security component affecting iOS before 10.2, macOS before 10.12.2, and watchOS before 3.1.3. The vulnerability allows remote attackers to spoof certificates via unspecified vectors, potentially enabling man-in-the-middle attacks or impersonation of trusted entities.
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.1.1<= 10.12.1<= 2.2.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the Apple device typeDetermine whether the device is an iPhone/iPad (iOS), Mac (macOS), or Apple Watch (watchOS). This will dictate which version check to perform.Affected if The device is an Apple product running an affected operating system.
-
Check iOS version on iPhone or iPadOn the device, go to Settings > General > About and check the 'Version' field. Compare this version number to the affected range.Affected if iOS version is 10.1.1 or earlier.
-
Check macOS version on MacClick the Apple menu in the top-left corner and select 'About This Mac'. The version number will be displayed in the window that opens.Affected if macOS version is 10.12.1 or earlier.
-
Check watchOS version on Apple WatchOpen the Watch app on the paired iPhone, go to My Watch > General > About, and check the 'Watch OS' version field.Affected if watchOS version is 2.2.2 or earlier.
-
Verify certificate verification behavior (optional)Inspect network traffic or verify that certificate chain validation is functioning properly when connecting to HTTPS sites. The vulnerability allows spoofed certificates to be accepted as valid.Affected if The device accepts certificates that should fail validation, indicating the vulnerability may be present.
A device is affected if it runs iOS 10.1.1 or earlier, macOS 10.12.1 or earlier, or watchOS 2.2.2 or earlier.
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: upgrade iOS to 10.2 or later, macOS to 10.12.2 or later, and watchOS to 3.1.3 or later.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7662 — 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-2016-7662 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