Workspace OneApplication · VMware
CVE-2018-6976
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 · uneditedThe VMware Content Locker for iOS prior to 4.14 contains a data protection vulnerability in the SQLite database. This vulnerability relates to unencrypted filenames and associated metadata in SQLite database for the Content Locker.
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 confidenceVMware Content Locker for iOS prior to version 4.14 stores filenames and associated metadata in its SQLite database without encryption. This exposes sensitive file information in plaintext within the database, which could be extracted if an attacker gains physical or logical access to the device.
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
Workspace OneApplication
< 4.14CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm VMware Content Locker is installedCheck the iOS device for the VMware Content Locker app or VMware Workspace One app. If managed via MDM, query the device inventory for installed applications.Affected if The app is present on the device
-
Identify the installed versionOn the iOS device, go to Settings > Apps > VMware Content Locker (or Workspace One) > Version to see the installed version number. Alternatively, query via MDM or Apple Configurator.Affected if Installed version is less than 4.14
-
Locate the SQLite databaseAccess the app container for VMware Content Locker/Workspace One on the iOS device. The database file is typically named with a .sqlite or .db extension within the app's Documents or Library folder.Affected if The database file exists in the app's local storage
-
Verify database encryption statusOpen the SQLite database file using a SQLite viewer or command-line tool. Inspect the database structure to determine if file names and metadata fields contain plaintext readable text.Affected if File names and metadata are stored in plaintext (unencrypted) within the database
-
Check for encrypted database implementationExamine the database for indicators of encryption such as encrypted pages, cipher headers, or absence of readable table data. In version 4.14+, the database should use SQLCipher or equivalent encryption.Affected if No encryption mechanism is present - database contents are readable in plaintext
A user is affected if VMware Content Locker/Workspace One is installed with a version lower than 4.14 and the local SQLite database contains plaintext file names and metadata.
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 data4.14
Upgrade VMware Content Locker for iOS to version 4.14 or later to obtain the encrypted database implementation.
Fix this in Workspace One
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6976 — 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-2018-6976 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