CVE-2017-7129
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 confidenceA vulnerability in SQLite versions prior to 3.19.3 allows remote attackers to cause denial of service through application crashes or potentially achieve unspecified other impact. This third-party library vulnerability affects multiple Apple operating systems (iOS, macOS, tvOS, watchOS) running versions before their respective patches.
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 the operating system and versionCheck the device OS version: iOS via Settings > General > About > Version; macOS via Apple menu > About This Mac; tvOS via Settings > General > About; watchOS via Watch app on paired iPhoneAffected if The version is at or below iOS 10.3.3, macOS 10.12.6, tvOS 10.2.2, or watchOS 3.2.3
-
Determine if SQLite is in useIdentify whether the system or application uses SQLite for data storage. Check for .sqlite, .db, or .sqlite3 files in application data directories, or review application dependencies for SQLite usageAffected if SQLite is used as a third-party library on an affected OS version
-
Check the bundled SQLite library versionFor applications using SQLite directly, locate the linked SQLite library (commonly libsqlite3.tbd or libsqlite3.dylib on Apple systems) and query its version via: otool -L <application> | grep sqlite, or check the library file version metadataAffected if The bundled SQLite library version is earlier than 3.19.3
-
Verify database file access from untrusted sourcesReview application code or system configurations to determine if SQLite databases are created from or opened with data from untrusted network sources, email attachments, or downloaded contentAffected if The application processes SQLite databases from untrusted remote sources on a vulnerable version
You are affected 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, and you use SQLite to process data from untrusted sources.
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 affected Apple devices to iOS 11+, macOS 10.13+, tvOS 11+, or watchOS 4+ to incorporate the patched SQLite library (3.19.3+). For embedded applications using SQLite directly, upgrade the SQLite library to version 3.19.3 or later.
iOS 11+, macOS 10.13 High Sierra+, tvOS 11+, watchOS 4+
- For iPhone OS: Upgrade to iOS 11 or later (iOS 11.0+)
- For Mac OS X: Upgrade to macOS 10.13 (High Sierra) or later
- For tvOS: Upgrade to tvOS 11 or later
- For watchOS: Upgrade to watchOS 4 or later
- After upgrading, verify the SQLite library version is 3.19.3 or later by checking system information or release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7129 — 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-7129 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