CVE-2017-7068
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.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 "libarchive" component. It allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow and application crash) via a crafted archive file.
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 confidenceA buffer overflow vulnerability exists in the libarchive library used by certain Apple products (iOS, macOS, tvOS, watchOS). Remote attackers can exploit this by tricking users into processing a specially crafted archive file, potentially achieving arbitrary code execution or causing application crashes.
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.2<= 10.12.5<= 10.2.1<= 3.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Check the installed iOS versionGo to Settings > General > About on the iOS device and note the Version numberAffected if The version is 10.3.2 or lower (any version up to and including 10.3.2)
-
Check the installed macOS versionRun 'sw_vers -productVersion' in Terminal, or go to Apple menu > About This Mac > VersionAffected if The version is 10.12.5 or lower (any version up to and including 10.12.5)
-
Check the installed tvOS versionGo to Settings > General > About on the Apple TV device and note the Version numberAffected if The version is 10.2.1 or lower (any version up to and including 10.2.1)
-
Check the installed watchOS versionOpen the Watch app on paired iPhone, go to My Watch > General > About, and note the VersionAffected if The version is 3.2.2 or lower (any version up to and including 3.2.2)
-
Identify third-party apps using libarchiveFor macOS, use 'otool -L <app_path>/Contents/MacOS/<app_binary>' or 'ldd' on Linux to list linked libraries and look for libarchive, or check the app vendor documentationAffected if Any third-party application that processes archive files is linked against a libarchive version earlier than the patched release (no specific version number provided in advisory)
You are affected if your device runs any 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, or if you use third-party applications linked to a vulnerable libarchive version.
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 dataUpdate all affected Apple devices to iOS 10.3.3+, macOS 10.12.6+, tvOS 10.2.2+, or watchOS 3.2.3+. For third-party applications using libarchive, rebuild against the patched libarchive version.
- 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-2017-7068 — 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-7068 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