CVE-2017-7133
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. The issue involves the "MobileBackup" component. It allows remote attackers to obtain sensitive cleartext information in opportunistic circumstances by leveraging read access to a backup archive that was supposed to have been encrypted.
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 confidenceIn iOS before version 11, the MobileBackup component fails to properly maintain encryption for backup archives under certain opportunistic circumstances. This allows an attacker with read access to a backup file that was expected to be encrypted to retrieve sensitive data in cleartext form.
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.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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Check the iOS version on the deviceOn the iOS device, go to Settings > General > About and look at the 'Version' field. Alternatively, connect the device to a computer and check via iTunes or Finder device info.Affected if The version displayed is 10.3.3 or earlier (any version up to and including 10.3.3)
-
Identify backup storage locationsLocate the iOS backup folder. On Mac: ~/Library/Application Support/MobileSync/Backup/. On Windows: %APPDATA%\Apple Computer\MobileSync\Backup\. Check for subdirectories with alphanumeric folder names.Affected if Any backup directories exist on the computer that sync or were created from an iOS device running version 10.3.3 or earlier
-
Verify backup encryption statusInspect the backup manifest file (Info.plist or Manifest.db) within the backup folder. Look for the 'IsEncrypted' key in Info.plist or query the database for encryption status. A value of '1' or true indicates the backup was set to use encryption.Affected if The backup is marked as encrypted but was created from an iOS 10.3.3 or earlier device, indicating potential exposure of cleartext data
A user is affected if their iOS device runs version 10.3.3 or earlier and they have backups that were expected to be encrypted stored on their computer, as those backups may contain cleartext sensitive data instead of properly encrypted content.
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 dataUpgrade affected iOS devices to version 11 or later to receive the patched MobileBackup component. Re-create any backups that may have been created during the vulnerable period.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7133 — 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-7133 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