ID CVE-2015-0922
Summary McAfee ePolicy Orchestrator (ePO) before 4.6.9 and 5.x before 5.1.2 uses the same secret key across different customers' installations, which allows attackers to obtain the administrator password by leveraging knowledge of the encrypted password.
References
Vulnerable Configurations
  • McAfee ePolicy Orchestrator 4.6.8
    cpe:2.3:a:mcafee:epolicy_orchestrator:4.6.8
  • McAfee ePolicy Orchestrator 5.0.0
    cpe:2.3:a:mcafee:epolicy_orchestrator:5.0.0
  • McAfee ePolicy Orchestrator 5.0.1
    cpe:2.3:a:mcafee:epolicy_orchestrator:5.0.1
  • McAfee ePolicy Orchestrator 5.1.0
    cpe:2.3:a:mcafee:epolicy_orchestrator:5.1.0
  • McAfee ePolicy Orchestrator 5.1.1
    cpe:2.3:a:mcafee:epolicy_orchestrator:5.1.1
CVSS
Base: 5.0 (as of 10-02-2015 - 15:46)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
metasploit via4
description This module will exploit an authenticated XXE vulnerability to read the keystore.properties off of the filesystem. This properties file contains an encrypted password that is set during installation. What is interesting about this password is that it is set as the same password as the database 'sa' user and of the admin user created during installation. This password is encrypted with a static key, and is encrypted using a weak cipher (ECB). By default, if installed with a local SQL Server instance, the SQL Server is listening on all interfaces. Recovering this password allows an attacker to potentially authenticate as the 'sa' SQL Server user in order to achieve remote command execution with permissions of the database process. If the administrator has not changed the password for the initially created account since installation, the attacker will have the password for this account. By default, 'admin' is recommended. Any user account can be used to exploit this, all that is needed is a valid credential. The most data that can be successfully retrieved is 255 characters due to length restrictions on the field used to perform the XXE attack.
id MSF:AUXILIARY/GATHER/MCAFEE_EPO_XXE
last seen 2019-03-24
modified 2018-09-15
published 2015-01-14
reliability Normal
reporter Rapid7
source https://github.com/rapid7/metasploit-framework/blob/master/modules/auxiliary/gather/mcafee_epo_xxe.rb
title McAfee ePolicy Orchestrator Authenticated XXE Credentials Exposure
nessus via4
NASL family Windows
NASL id MCAFEE_EPO_SB10095.NASL
description The version of McAfee ePolicy Orchestrator (ePO) installed on the remote Windows host is 4.x prior to 4.6.9 or 5.x prior to 5.1.2. It is, therefore, affected by multiple vulnerabilities : - An XXE (XML External Entity) injection vulnerability exists in the Server Task Log due to an incorrectly configured XML parser accepting XML external entities from an untrusted source. A remote, authenticated attacker, by sending specially crafted XML data via the 'conditionXML' parameter, can gain access to arbitrary files. (CVE-2015-0921) - An information disclosure vulnerability exists due to the use of a shared secret key to encrypt password information. A remote attacker with knowledge of the key can decrypt the administrator password. (CVE-2015-0922)
last seen 2019-02-21
modified 2018-11-15
plugin id 81106
published 2015-01-30
reporter Tenable
source https://www.tenable.com/plugins/index.php?view=single&id=81106
title McAfee ePolicy Orchestrator 4.x < 4.6.9 / 5.x < 5.1.2 Multiple Vulnerabilities (SB10095)
refmap via4
bid 72298
confirm https://kc.mcafee.com/corporate/index?page=content&id=SB10095
fulldisc
  • 20150106 McAfee ePolicy Orchestrator Authenticated XXE and Credential Exposure
  • 20150112 Re: McAfee ePolicy Orchestrator Authenticated XXE and Credential Exposure
misc
sectrack 1031519
xf macafee-cve20150922-info-disc(99949)
Last major update 02-01-2017 - 21:59
Published 09-01-2015 - 13:59
Last modified 07-09-2017 - 21:29
Back to Top