Security readout for executives and security teams
Plain-English summary
CVE-2018-11737 is a memory-read flaw in The Sleuth Kit library when handling NTFS data. A crafted file system image could cause information disclosure or crash the consuming process. Public sources do not provide a CVSS score, confirmed exploitation, or specific fixed version details.
Executive priority
Treat this as a targeted exposure review, not an emergency based on current evidence. Prioritize if TSK processes untrusted NTFS data in production, investigative, or automated pipelines.
Technical view
The issue is an out-of-bounds read in libtskfs.a, function ntfs_fix_idxrec in tsk/fs/ntfs_dent.cpp, affecting TSK releases 4.0.2 through 4.6.1. The CVE states impact may include information disclosure or denial of service by reading unmapped memory.
Likely exposure
Exposure is most likely where The Sleuth Kit 4.0.2 through 4.6.1, or software embedding libtskfs.a, processes untrusted or attacker-supplied NTFS file system data.
Exploitation context
The provided sources do not show active exploitation, public weaponization, or KEV listing. Exploitation would require getting vulnerable TSK code to parse malicious NTFS data; exact practical exploitability is not established in the bundle.
Researcher notes
The record names the vulnerable function and impact class but lacks CVSS, CWE, exploit confirmation, and explicit fix metadata. Validate version exposure first, then consult upstream Sleuth Kit issue history before assigning operational severity.
Mitigation direction
- Inventory TSK and embedded libtskfs.a versions in affected workflows.
- Check upstream Sleuth Kit guidance for fixed releases or patches.
- Avoid processing untrusted NTFS images with affected versions where possible.
- Isolate parsing jobs to limit crash or information-disclosure impact.
Validation and detection
- Confirm whether TSK version is 4.0.2 through 4.6.1.
- Check dependent tools for bundled or statically linked libtskfs.a.
- Review NTFS parsing workflows for untrusted input exposure.
- Monitor upstream issue and CVE records for remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-11737 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/sleuthkit/sleuthkit/issues/1266CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.