What is the severity of CVE-2017-4942?

CVE-2017-4942 is considered to be of high severity due to its potential to allow unauthorized access to sensitive end-user device details.

How do I fix CVE-2017-4942?

To fix CVE-2017-4942, it is recommended to update VMware AirWatch Console to the latest version available beyond 9.2.2.0.

Who is affected by CVE-2017-4942?

CVE-2017-4942 affects users of VMware AirWatch Console versions 9.0 to 9.2.2.0.

What could be the impact of CVE-2017-4942?

The exploitation of CVE-2017-4942 could lead to unauthorized disclosure of end-user device details to administrators without proper authorization.

Is there a workaround for CVE-2017-4942?

Currently, there is no specific workaround for CVE-2017-4942, and updating to a patched version of the software is necessary for protection.

Vulnerability/
CVE-2017-4942

medium

4.9

13/12/2017

16/9/2024

CVE-2017-4942

First published: Wed Dec 13 2017(Updated: )

VMware AirWatch Console (AWC) contains a Broken Access Control vulnerability. Successful exploitation of this issue could result in end-user device details being disclosed to an unauthorized administrator.

Credit: security@vmware.com

Affected Software	Affected Version	How to fix
VMware AirWatch Console	>=9.0<9.2.2.0

Remedy

https://www.vmware.com/security/advisories/VMSA-2017-0020.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-4942?
CVE-2017-4942 is considered to be of high severity due to its potential to allow unauthorized access to sensitive end-user device details.
How do I fix CVE-2017-4942?
To fix CVE-2017-4942, it is recommended to update VMware AirWatch Console to the latest version available beyond 9.2.2.0.
Who is affected by CVE-2017-4942?
CVE-2017-4942 affects users of VMware AirWatch Console versions 9.0 to 9.2.2.0.
What could be the impact of CVE-2017-4942?
The exploitation of CVE-2017-4942 could lead to unauthorized disclosure of end-user device details to administrators without proper authorization.
Is there a workaround for CVE-2017-4942?
Currently, there is no specific workaround for CVE-2017-4942, and updating to a patched version of the software is necessary for protection.

collector/nvd-index
agent/type
agent/severity
agent/remedy
agent/author
agent/references
agent/softwarecombine
agent/description
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
vendor/vmware
canonical/vmware airwatch console
version/vmware airwatch console/9.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-4942?
CVE-2017-4942 is considered to be of high severity due to its potential to allow unauthorized access to sensitive end-user device details.
How do I fix CVE-2017-4942?
To fix CVE-2017-4942, it is recommended to update VMware AirWatch Console to the latest version available beyond 9.2.2.0.
Who is affected by CVE-2017-4942?
CVE-2017-4942 affects users of VMware AirWatch Console versions 9.0 to 9.2.2.0.
What could be the impact of CVE-2017-4942?
The exploitation of CVE-2017-4942 could lead to unauthorized disclosure of end-user device details to administrators without proper authorization.
Is there a workaround for CVE-2017-4942?
Currently, there is no specific workaround for CVE-2017-4942, and updating to a patched version of the software is necessary for protection.