CVE-2017-2792
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn exploitable heap corruption vulnerability exists in the iBldDirInfo functionality of Antenna House DMC HTMLFilter used by MarkLogic 8.0-6. A specially crafted xls file can cause a heap corruption resulting in arbitrary code execution. An attacker can provide a malicious xls file to trigger this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA heap corruption vulnerability exists in the iBldDirInfo function of Antenna House DMC HTMLFilter (used by MarkLogic 8.0-6). When processing a specially crafted malicious XLS file, the parser corrupts heap memory, potentially allowing an attacker to achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.0-6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm MarkLogic installationIdentify if MarkLogic Server is running in the environment by checking for MarkLogic processes (e.g., 'ps -ef | grep -i marklogic' on Linux or checking Windows services) or looking for MarkLogic installation directories.Affected if MarkLogic Server is installed and running.
-
Determine MarkLogic versionRun the command to retrieve the MarkLogic version, such as 'xdmp:version()' in XQuery, using the admin interface, or checking the MarkLogic installation directory for version files. Compare the installed version against the affected range: 8.0-6 and earlier versions.Affected if The installed version is 8.0-6 or any version earlier than 8.0-6.
-
Verify XLS file processing capabilityCheck if the MarkLogic server is configured to accept or process XLS files. This may involve reviewing MarkLogic configuration settings, application logic, or checking for XLS-related transformation or ingestion pipelines.Affected if The environment processes or can process XLS files through MarkLogic.
-
Inspect for anomalous XLS file handlingReview MarkLogic server logs (typically in the 'Logs' directory under the MarkLogic installation) for errors, crashes, or heap-related messages occurring during XLS file processing. Look for patterns indicating heap corruption or unexpected termination.Affected if Logs show heap corruption errors, crashes, or abnormal behavior when processing XLS files.
A user is affected if MarkLogic version 8.0-6 or earlier is installed AND the system processes XLS files, with potential indicators visible in server logs showing corruption or crashes during XLS handling.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict processing of untrusted XLS files and apply vendor security patches or upgrade MarkLogic to a patched version. Network filtering can also reduce exposure by limiting where malicious files can be delivered.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-2792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data