CVE Vulnerabilities


Out-of-bounds Read

Published: Jun 05, 2018 | Modified: Jul 13, 2018
CVSS 3.x
CVSS 2.x

An issue was discovered in libtskbase.a in The Sleuth Kit (TSK) from release 4.0.2 through to 4.6.1. An out-of-bounds read of a memory region was found in the function tsk_UTF16toUTF8 in tsk/base/tsk_unicode.c which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service attack.


The software reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
The_sleuth_kit Sleuthkit 4.0.2 4.6.1
Sleuthkit Ubuntu artful *
Sleuthkit Ubuntu bionic *
Sleuthkit Ubuntu cosmic *
Sleuthkit Ubuntu devel *
Sleuthkit Ubuntu disco *
Sleuthkit Ubuntu eoan *
Sleuthkit Ubuntu focal *
Sleuthkit Ubuntu groovy *
Sleuthkit Ubuntu hirsute *
Sleuthkit Ubuntu impish *
Sleuthkit Ubuntu jammy *
Sleuthkit Ubuntu trusty *
Sleuthkit Ubuntu upstream *
Sleuthkit Ubuntu xenial *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.