CVE Vulnerabilities


Out-of-bounds Read

Published: Oct 13, 2019 | Modified: Feb 28, 2023
CVSS 3.x
CVSS 2.x

Mat_VarReadNextInfo4 in mat4.c in MATIO 1.5.17 omits a certain 0 character, leading to a heap-based buffer over-read in strdup_vprintf when uninitialized memory is accessed.


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

Affected Software

Name Vendor Start Version End Version
Matio Matio_project 1.5.17 (including) 1.5.17 (including)
Libmatio Ubuntu bionic *
Libmatio Ubuntu disco *
Libmatio Ubuntu eoan *
Libmatio Ubuntu esm-apps/bionic *
Libmatio Ubuntu esm-apps/focal *
Libmatio Ubuntu esm-apps/xenial *
Libmatio Ubuntu focal *
Libmatio Ubuntu trusty *
Libmatio Ubuntu trusty/esm *
Libmatio Ubuntu upstream *
Libmatio Ubuntu xenial *
Libpdl-io-matlab-perl Ubuntu bionic *
Libpdl-io-matlab-perl Ubuntu disco *
Libpdl-io-matlab-perl Ubuntu eoan *
Libpdl-io-matlab-perl Ubuntu groovy *
Libpdl-io-matlab-perl Ubuntu hirsute *
Libpdl-io-matlab-perl Ubuntu impish *
Libpdl-io-matlab-perl Ubuntu kinetic *
Libpdl-io-matlab-perl Ubuntu lunar *
Libpdl-io-matlab-perl Ubuntu trusty *
Libpdl-io-matlab-perl Ubuntu xenial *
Mldemos Ubuntu disco *
Mldemos Ubuntu eoan *
Mldemos Ubuntu trusty *
Mldemos 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.