# CVE-2017-4932: Privilege escalation in VMware AirWatch Launcher for Android (AWL)

> Attackers can escalate privileges from the launcher UI context menu to native UI functionality in VMware AirWatch Launcher for Android.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wpgg-v2pr-g379

## What is CVE-2017-4932?

CVE-2017-4932 is a high-severity vulnerability in VMware AirWatch Launcher for Android (AWL), published on 16 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VMware AirWatch Launcher for Android prior to 3.2.2 contains a vulnerability that could allow an escalation of privilege from the launcher UI context menu to native UI functionality and privilege. Successful exploitation of this issue could result in an escalation of privilege.

## Which versions are affected by CVE-2017-4932?

It affects 1 product.


Products: Vmware Airwatch Launcher.

## How do I fix CVE-2017-4932?

No fix has been published for CVE-2017-4932 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-4932 being exploited?

There is no known exploitation of CVE-2017-4932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-4932 and fix it if it is affected.

What it is: CVE-2017-4932 is a high-severity vulnerability in VMware AirWatch Launcher for Android (AWL), published on 16 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-4932 in the wild and no public exploit code.

Affected product: VMware AirWatch Launcher for Android (AWL). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-4932/ (Markdown: https://insights.sbomify.com/CVE-2017-4932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-4932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-4932
- OSV: https://osv.dev/vulnerability/CVE-2017-4932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-4932/
Summaries are generated and may contain mistakes; the official description above is the record.