CVE Vulnerabilities

CVE-2021-3504

Out-of-bounds Read

Published: May 11, 2021 | Modified: Nov 07, 2023
CVSS 3.x
5.4
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:P
RedHat/V2
RedHat/V3
5.4 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
Ubuntu
MEDIUM

A flaw was found in the hivex library in versions before 1.3.20. It is caused due to a lack of bounds check within the hivex_open function. An attacker could input a specially crafted Windows Registry (hive) file which would cause hivex to read memory beyond its normal bounds or cause the program to crash. The highest threat from this vulnerability is to system availability.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Hivex Redhat * 1.3.20 (excluding)
Red Hat Enterprise Linux 7 RedHat hivex-0:1.3.10-6.11.el7_9 *
Red Hat Enterprise Linux 8 RedHat virt-devel:rhel-8040020210721215855.522a0ee4 *
Red Hat Enterprise Linux 8 RedHat virt:rhel-8040020210721215855.522a0ee4 *
Hivex Ubuntu bionic *
Hivex Ubuntu devel *
Hivex Ubuntu esm-apps/jammy *
Hivex Ubuntu esm-apps/noble *
Hivex Ubuntu esm-apps/xenial *
Hivex Ubuntu focal *
Hivex Ubuntu groovy *
Hivex Ubuntu hirsute *
Hivex Ubuntu impish *
Hivex Ubuntu jammy *
Hivex Ubuntu kinetic *
Hivex Ubuntu lunar *
Hivex Ubuntu mantic *
Hivex Ubuntu noble *
Hivex Ubuntu oracular *
Hivex Ubuntu trusty *
Hivex Ubuntu trusty/esm *
Hivex Ubuntu upstream *
Hivex 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.

References