What is the severity of CVE-2012-4587?

CVE-2012-4587 is classified as a medium severity vulnerability.

How do I fix CVE-2012-4587?

To fix CVE-2012-4587, upgrade to McAfee Enterprise Mobility Manager Agent version 4.8 or later and Server version 10.1 or later.

What are the risks associated with CVE-2012-4587?

The risks associated with CVE-2012-4587 include the potential for remote attackers to spoof the EMM server and discover user passwords.

Which software versions are affected by CVE-2012-4587?

CVE-2012-4587 affects McAfee Enterprise Mobility Manager versions prior to 4.8 and McAfee Enterprise Mobility Manager Agent versions prior to 10.1.

Is there a workaround for CVE-2012-4587?

There are no known effective workarounds for CVE-2012-4587; patching is recommended.

Vulnerability/
CVE-2012-4587

low

3.5

CWE

264

22/8/2012

6/8/2024

CVE-2012-4587

First published: Wed Aug 22 2012(Updated: )

McAfee Enterprise Mobility Manager (EMM) Agent before 4.8 and Server before 10.1, when one-time provisioning (OTP) mode is enabled, have an improper dependency on DNS SRV records, which makes it easier for remote attackers to discover user passwords by spoofing the EMM server, as demonstrated by a password entered on an iOS device.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
McAfee Enterprise Mobility Manager	<=4.7
Mcafee Enterprise Mobility Manager Agent	<=10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2012-4587?
CVE-2012-4587 is classified as a medium severity vulnerability.
How do I fix CVE-2012-4587?
To fix CVE-2012-4587, upgrade to McAfee Enterprise Mobility Manager Agent version 4.8 or later and Server version 10.1 or later.
What are the risks associated with CVE-2012-4587?
The risks associated with CVE-2012-4587 include the potential for remote attackers to spoof the EMM server and discover user passwords.
Which software versions are affected by CVE-2012-4587?
CVE-2012-4587 affects McAfee Enterprise Mobility Manager versions prior to 4.8 and McAfee Enterprise Mobility Manager Agent versions prior to 10.1.
Is there a workaround for CVE-2012-4587?
There are no known effective workarounds for CVE-2012-4587; patching is recommended.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/last-modified-date
agent/severity
agent/weakness
agent/tags
agent/first-publish-date
agent/event
agent/description
agent/source
vendor/mcafee
canonical/mcafee enterprise mobility manager
version/mcafee enterprise mobility manager/4.7
canonical/mcafee enterprise mobility manager agent
version/mcafee enterprise mobility manager agent/10.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-2012-4587?
CVE-2012-4587 is classified as a medium severity vulnerability.
How do I fix CVE-2012-4587?
To fix CVE-2012-4587, upgrade to McAfee Enterprise Mobility Manager Agent version 4.8 or later and Server version 10.1 or later.
What are the risks associated with CVE-2012-4587?
The risks associated with CVE-2012-4587 include the potential for remote attackers to spoof the EMM server and discover user passwords.
Which software versions are affected by CVE-2012-4587?
CVE-2012-4587 affects McAfee Enterprise Mobility Manager versions prior to 4.8 and McAfee Enterprise Mobility Manager Agent versions prior to 10.1.
Is there a workaround for CVE-2012-4587?
There are no known effective workarounds for CVE-2012-4587; patching is recommended.