CVE-2017-7130
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 is affected. macOS before 10.13 is affected. tvOS before 11 is affected. watchOS before 4 is affected. The issue involves the third-party "SQLite" product. Versions before 3.19.3 allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact.
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 vulnerability in the third-party SQLite database library affecting versions prior to 3.19.3. The flaw is present in multiple Apple operating systems (iOS before 11, macOS before 10.13, tvOS before 11, watchOS before 4). Remote attackers can exploit this to cause denial of service through application crashes or potentially achieve unspecified other impact.
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.3.3<= 10.12.6<= 10.2.2<= 3.2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple device typeDetermine whether the device is an iPhone, iPad (iOS), Mac (macOS), Apple TV (tvOS), or Apple Watch (watchOS). Check the physical device or system report.Affected if Device is an iPhone, Mac, Apple TV, or Apple Watch running the affected Apple OS versions
-
Check installed iOS version on iPhone/iPadGo to Settings > General > About on the device and note the version number displayed next to 'Version'. Alternatively, connect the device to a computer and check via iTunes or Finder.Affected if iOS version is 10.3.3 or earlier (versions through 10.3.3 are affected)
-
Check installed macOS versionClick the Apple menu > About This Mac. The version number appears below the macOS name (such as '10.12.6').Affected if macOS version is 10.12.6 or earlier (versions through 10.12.6 are affected)
-
Check installed tvOS or watchOS versionOn Apple TV: go to Settings > General > About > Version. On Apple Watch: open the Watch app on iPhone > General > About > watchOS Version.Affected if tvOS version is 10.2.2 or earlier, or watchOS version is 3.2.3 or earlier
-
Compare your version to affected rangesMatch your identified OS version against the CVE-affected ranges: iOS <= 10.3.3, macOS <= 10.12.6, tvOS <= 10.2.2, watchOS <= 3.2.3.Affected if Your installed OS version falls at or below the maximum affected version for your device type
If your device runs iOS 10.3.3 or earlier, macOS 10.12.6 or earlier, tvOS 10.2.2 or earlier, or watchOS 3.2.3 or earlier, your environment contains the vulnerable SQLite library and is affected by CVE-2017-7130.
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.
dbcve · scopedUpgrade SQLite to version 3.19.3 or later, and update affected Apple devices to iOS 11, macOS 10.13, tvOS 11, or watchOS 4 respectively to incorporate the patched library.
iOS 11+, macOS High Sierra (10.13)+, tvOS 11+, watchOS 4+ (all include SQLite 3.19.3 or later)
- Back up your device data before performing any upgrade
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 11 or later
- For Mac: Go to System Preferences > Software Update and install macOS High Sierra (10.13) or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 11 or later
- For Apple Watch: Pair with iPhone and update watchOS through the Watch app to version 4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7130 — 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-7130 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