MarkLogic 8.0-6 Antenna House DMC HTMLFilter XLS File memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in MarkLogic 8.0-6 and classified as critical. Affected is an unknown function of the component Antenna House DMC HTMLFilter. Performing a manipulation as part of XLS File results in memory corruption. This vulnerability is reported as CVE-2017-2783. The attack requires a local approach. No exploit exists.
Details
A vulnerability classified as critical has been found in MarkLogic 8.0-6. This affects an unknown part of the component Antenna House DMC HTMLFilter. The manipulation as part of a XLS File leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An exploitable heap corruption vulnerability exists in the FillRowFormat functionality of Antenna House DMC HTMLFilter that is shipped with MarkLogic 8.0-6. A specially crafted xls file can cause a heap corruption resulting in arbitrary code execution. An attacker can send/provide malicious xls file to trigger this vulnerability.
The bug was discovered 05/04/2017. The weakness was disclosed 05/23/2017 (Website). It is possible to read the advisory at talosintelligence.com. This vulnerability is uniquely identified as CVE-2017-2783 since 12/01/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 19 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-101730, VDB-101729 and VDB-101728 are pretty similar. Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 8.3
CNA Vector (Talos): 🔍
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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/01/2016 🔍05/04/2017 🔍
05/23/2017 🔍
05/23/2017 🔍
05/24/2017 🔍
12/07/2022 🔍
Sources
Advisory: talosintelligence.comStatus: Not defined
CVE: CVE-2017-2783 (🔍)
GCVE (CVE): GCVE-0-2017-2783
GCVE (VulDB): GCVE-100-101727
OSVDB: - CVE-2017-2783 - Marklogic - Marklogic - Medium
See also: 🔍
Entry
Created: 05/24/2017 08:42Updated: 12/07/2022 09:35
Changes: 05/24/2017 08:42 (57), 10/02/2020 16:54 (2), 12/07/2022 09:35 (14)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.