CVE Vulnerabilities

CVE-2022-2127

Out-of-bounds Read

Published: Jul 20, 2023 | Modified: Sep 16, 2024
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
5.9 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

An out-of-bounds read vulnerability was found in Samba due to insufficient length checks in winbindd_pam_auth_crap.c. When performing NTLM authentication, the client replies to cryptographic challenges back to the server. These replies have variable lengths, and Winbind fails to check the lan manager response length. When Winbind is used for NTLM authentication, a maliciously crafted request can trigger an out-of-bounds read in Winbind, possibly resulting in a crash.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Samba Samba 4.16.0 (including) 4.16.10 (excluding)
Samba Samba 4.17.0 (including) 4.17.9 (excluding)
Samba Samba 4.18.0 (including) 4.18.4 (excluding)
Samba Ubuntu bionic *
Samba Ubuntu devel *
Samba Ubuntu focal *
Samba Ubuntu jammy *
Samba Ubuntu kinetic *
Samba Ubuntu lunar *
Samba Ubuntu mantic *
Samba Ubuntu noble *
Samba Ubuntu oracular *
Samba Ubuntu trusty *
Samba Ubuntu xenial *
Red Hat Enterprise Linux 8 RedHat samba-0:4.18.6-1.el8 *
Red Hat Enterprise Linux 8 RedHat samba-0:4.18.6-1.el8 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat samba-0:4.15.5-15.el8_6 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat samba-0:4.17.5-5.el8_8 *
Red Hat Enterprise Linux 9 RedHat samba-0:4.18.6-100.el9 *
Red Hat Enterprise Linux 9 RedHat samba-0:4.18.6-100.el9 *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 8 RedHat samba-0:4.15.5-15.el8_6 *

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