Trend Micro Control Manager 6.0 xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Trend Micro Control Manager 6.0 and classified as problematic. The impacted element is an unknown function. Performing a manipulation results in xml external entity reference. This vulnerability is cataloged as CVE-2018-3600. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Trend Micro Control Manager 6.0 (Log Management Software). It has been classified as problematic. This affects an unknown part. The manipulation with an unknown input leads to a xml external entity reference vulnerability. CWE is classifying the issue as CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. This is going to have an impact on confidentiality. The summary by CVE is:
A external entity processing information disclosure (XXE) vulnerability in Trend Micro Control Manager 6.0 could allow a remote attacker to disclose sensitive information on vulnerable installations.
The bug was discovered 01/09/2018. The weakness was shared 02/09/2018 (Website). The advisory is shared at success.trendmicro.com. This vulnerability is uniquely identified as CVE-2018-3600 since 12/27/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/03/2020).
The vulnerability was handled as a non-public zero-day exploit for at least 31 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.
The entries VDB-113110, VDB-113111, VDB-113112 and VDB-113113 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.trendmicro.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
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
Class: Xml external entity referenceCWE: CWE-611 / CWE-610
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/27/2017 🔍01/09/2018 🔍
02/09/2018 🔍
02/09/2018 🔍
02/10/2018 🔍
01/03/2020 🔍
Sources
Vendor: trendmicro.comAdvisory: success.trendmicro.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-3600 (🔍)
GCVE (CVE): GCVE-0-2018-3600
GCVE (VulDB): GCVE-100-113109
See also: 🔍
Entry
Created: 02/10/2018 11:00Updated: 01/03/2020 17:24
Changes: 02/10/2018 11:00 (57), 01/03/2020 17:24 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.