dbcve.org
Airwatch AgentApplication · VMware

CVE-2018-6968

CRITICAL · 10.0 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to 6.5.2 / 8.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 VMware AirWatch Agent for Android prior to 8.2 and AirWatch Agent for Windows Mobile prior to 6.5.2 contain a remote code execution vulnerability in real time File Manager capabilities. This vulnerability may allow for unauthorized creation and execution of files in the Agent sandbox and other publicly accessible directories such as those on the SD card by a malicious administrator.

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 Android (prior to 8.2) and Windows Mobile (prior to 6.5.2) contains an RCE vulnerability in the real-time File Manager component. This flaw allows a malicious administrator to create and execute arbitrary files within the agent's sandbox and publicly accessible directories such as SD cards, enabling remote code execution on enrolled devices.

MitigationUpgrade AirWatch Agent for Android to version 8.2 or later and Windows Mobile to version 6.5.2 or later. Until patched, restrict administrative console access and implement monitoring for suspicious file operations in the MDM console.

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
Airwatch AgentApplication
Affected:< 6.5.2< 8.2

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Check the installed AirWatch Agent version on Android devices
    Navigate to Settings > Apps > AirWatch Agent (or AirWatch Android Agent) and view the Version information. Alternatively, open the AirWatch Agent app and look for version details in the About or Settings section.
    Affected if The displayed version is lower than 8.2 (for example, 8.1.x, 8.0.x, or any version below 8.2)
  2. Check the installed AirWatch Agent version on Windows Mobile devices
    Navigate to Settings > Apps > Apps list > AirWatch Agent and view the Version details, or check in the agent application's About/Info section.
    Affected if The displayed version is lower than 6.5.2 (for example, 6.5.1, 6.5.0, or any version below 6.5.2)
  3. Verify if the real-time File Manager feature is enabled in the MDM console
    Log into the AirWatch (Workspace ONE UEM) administrative console and navigate to the device profile or agent configuration settings. Look for File Manager, Remote File Management, or similar real-time file operation settings under the agent configuration profile.
    Affected if The File Manager or real-time file management feature is enabled or configured for the device group
  4. Check if the agent has file system access permissions
    On the device, check the AirWatch Agent permissions in Settings > Apps > AirWatch Agent > Permissions. Specifically look for Storage, Files and Media, or SD Card access permissions that are granted.
    Affected if The agent has Storage, Files and Media, or SD Card read/write permissions enabled

A device is affected if the AirWatch Agent version is below 8.2 on Android or below 6.5.2 on Windows Mobile AND the real-time File Manager feature is enabled with file system access permissions granted.

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.

dbcve · scoped
Upgrade available Upgrade to 6.5.2 / 8.2 or later
Fixed in 6.5.28.2
Interim mitigation

Upgrade AirWatch Agent for Android to version 8.2 or later and Windows Mobile to version 6.5.2 or later. Until patched, restrict administrative console access and implement monitoring for suspicious file operations in the MDM console.

Recommended fix Moderate confidence

AirWatch Agent for Android: 8.2+; AirWatch Agent for Windows Mobile: 6.5.2+

  1. Identify the affected platform: Android or Windows Mobile
  2. Check the current version of the installed AirWatch Agent
  3. For Android: Upgrade to AirWatch Agent version 8.2 or later from VMware Workspace ONE or AirWatch official distribution channels
  4. For Windows Mobile: Upgrade to AirWatch Agent version 6.5.2 or later
  5. Test the upgraded agent in a staging environment before production deployment
  6. Verify the upgrade was successful by checking the agent version
Caveat Standard enterprise software upgrade considerations apply - test compatibility with existing MDM infrastructure and enrolled devices before rolling out widely

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Airwatch Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6968 — 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-6968 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