dbcve.org
Intelligent HubApplication · VMware

CVE-2018-6975

MEDIUM · 5.5 CVSS v3.0 Published 2018-09-11
Fix available
A fix is available. Upgrade to 5.8.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
The AirWatch Agent for iOS prior to 5.8.1 contains a data protection vulnerability whereby the files and keychain entries in the Agent are not 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 confidence

The AirWatch Agent for iOS versions prior to 5.8.1 fails to encrypt sensitive data stored in local files and keychain entries, leaving them accessible in plaintext. This allows attackers with physical device access or malicious apps with sufficient permissions to potentially read confidential information such as credentials or sensitive business data stored by the agent.

MitigationUpgrade AirWatch Agent for iOS to version 5.8.1 or later, which implements proper encryption for files and keychain entries. Verify the upgrade in a test environment before production deployment.

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
Intelligent HubApplication
Affected:< 5.8.1

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed VMware Intelligent Hub version
    Open the app on the iOS device, navigate to Settings > About, or check the iOS Settings > General > Device Management for the installed profile version. Compare the version number to 5.8.1.
    Affected if The displayed version is below 5.8.1 (for example, 5.7.x, 5.6.x, or earlier)
  2. Identify local storage location
    On a jailbroken device or through a forensics tool, navigate to the app's sandboxed container (typically /var/mobile/Containers/Application/ or via Filza file manager if available). Look for folders named Documents, Library, or tmp within the AirWatch or Intelligent Hub app directory.
    Affected if The app directory exists and contains any data files
  3. Inspect plaintext file contents
    Open any .plist, .json, .xml, or .txt files found in the app's Documents or Library folders using a text editor or plist viewer. Look for patterns indicating credentials, API keys, business data, or configuration values stored in plaintext.
    Affected if Sensitive data such as usernames, passwords, tokens, or business information is readable in plaintext within these files
  4. Examine keychain entries
    Use a keychain viewer tool (such as Keychain Dumper on jailbroken devices or iMazing, or check via iOS Settings > Passwords > AirWatch if accessible). Locate entries associated with the AirWatch or Intelligent Hub bundle identifier.
    Affected if Keychain entries contain sensitive data (credentials, tokens) that are stored without encryption protection or are accessible without proper authentication

You are affected if the installed VMware Intelligent Hub version is below 5.8.1 AND the app stores sensitive data in unencrypted local files or keychain entries accessible to unauthorized access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 5.8.1 or later
Fixed in 5.8.1
Interim mitigation

Upgrade AirWatch Agent for iOS to version 5.8.1 or later, which implements proper encryption for files and keychain entries. Verify the upgrade in a test environment before production deployment.

Fix this in Intelligent Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-6975 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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