dbcve.org
Iphone OsOperating system · Apple

CVE-2017-7080

HIGH · 7.5 CVSS v3.0 Published 2017-10-23
Fix available
A fix is available. Upgrade to after 10.12.6 or later.
See remediation →
84/100
Remediation priority · High
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 11 is affected. macOS before 10.13 is affected. tvOS before 11 is affected. watchOS before 4 is affected. The issue involves the "Security" component. It allows remote attackers to bypass intended certificate-trust restrictions via a revoked X.509 certificate.

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

The Security component in Apple iOS, macOS, tvOS, and watchOS failed to properly validate certificate trust, allowing remote attackers to bypass intended certificate-trust restrictions by using a revoked X.509 certificate.

MitigationUpdate affected Apple devices to iOS 11 or later, macOS 10.13 or later, tvOS 11 or later, and watchOS 4 or later to remediate the certificate validation bypass.

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.3
Mac Os XOperating system
Affected:<= 10.12.6
TvosOperating system
Affected:<= 10.2.2
WatchosOperating system
Affected:<= 3.2.3

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
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 checks

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

  1. Check iOS version on iPhone or iPad
    Go to Settings > General > About > Version and note the displayed version number
    Affected if The version is 10.3.3 or lower
  2. Check macOS version on Mac
    Click the Apple menu > About This Mac and note the version displayed under macOS
    Affected if The version is 10.12.6 or lower
  3. Check tvOS version on Apple TV
    Go to Settings > General > About > Version and note the displayed version number
    Affected if The version is 10.2.2 or lower
  4. Check watchOS version on Apple Watch
    Open the Watch app on paired iPhone, go to General > About, and note the watchOS version
    Affected if The version is 3.2.3 or lower

If any of the detected OS versions fall at or below the affected thresholds for their respective platform, the device is vulnerable to the certificate validation bypass.

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.

From vendor data
Upgrade available Upgrade to a release after 10.12.6
Interim mitigation

Update affected Apple devices to iOS 11 or later, macOS 10.13 or later, tvOS 11 or later, and watchOS 4 or later to remediate the certificate validation bypass.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-7080 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