McAfee Threat Intelligence Exchange up to 2.1.0 ePolicy Orchestrator XML Reflected code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as problematic has been found in McAfee Threat Intelligence Exchange up to 2.1.0. The impacted element is an unknown function of the component ePolicy Orchestrator XML Handler. The manipulation leads to code injection (Reflected). This vulnerability is traded as CVE-2017-3907. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in McAfee Threat Intelligence Exchange up to 2.1.0 and classified as problematic. This issue affects some unknown processing of the component ePolicy Orchestrator XML Handler. The manipulation with an unknown input leads to a code injection vulnerability (Reflected). Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is integrity. The summary by CVE is:
Code Injection vulnerability in the ePolicy Orchestrator (ePO) extension in McAfee Threat Intelligence Exchange (TIE) Server 2.1.0 and earlier allows remote attackers to execute arbitrary HTML code to be reflected in the response web page via unspecified vector.
The bug was discovered 03/19/2018. The weakness was shared 06/13/2018 (Website). The advisory is shared at kc.mcafee.com. The identification of this vulnerability is CVE-2017-3907 since 12/26/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/27/2023). MITRE ATT&CK project uses the attack technique T1059 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 86 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.mcafee.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.4
CNA Vector (McAfee): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: ReflectedClass: Code injection / Reflected
CWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/26/2016 🔍03/19/2018 🔍
06/13/2018 🔍
06/13/2018 🔍
06/14/2018 🔍
03/27/2023 🔍
Sources
Vendor: mcafee.comAdvisory: kc.mcafee.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-3907 (🔍)
GCVE (CVE): GCVE-0-2017-3907
GCVE (VulDB): GCVE-100-119489
Entry
Created: 06/14/2018 08:37Updated: 03/27/2023 09:28
Changes: 06/14/2018 08:37 (57), 02/19/2020 08:11 (2), 03/27/2023 09:28 (14)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.