CVE Vulnerabilities

CVE-2022-3437

Heap-based Buffer Overflow

Published: Jan 12, 2023 | Modified: Nov 21, 2024
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/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:L/UI:N/S:U/C:N/I:H/A:L
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

A heap-based buffer overflow vulnerability was found in Samba within the GSSAPI unwrap_des() and unwrap_des3() routines of Heimdal. The DES and Triple-DES decryption routines in the Heimdal GSSAPI library allow a length-limited write buffer overflow on malloc() allocated memory when presented with a maliciously small packet. This flaw allows a remote user to send specially crafted malicious data to the application, possibly resulting in a denial of service (DoS) attack.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

NameVendorStart VersionEnd Version
SambaSamba4.0.0 (including)4.15.11 (excluding)
SambaSamba4.16.0 (including)4.16.6 (excluding)
SambaSamba4.17.0 (including)4.17.2 (excluding)
HeimdalUbuntubionic*
HeimdalUbuntuesm-apps/jammy*
HeimdalUbuntuesm-infra-legacy/trusty*
HeimdalUbuntuesm-infra/bionic*
HeimdalUbuntuesm-infra/focal*
HeimdalUbuntuesm-infra/xenial*
HeimdalUbuntufocal*
HeimdalUbuntujammy*
HeimdalUbuntukinetic*
HeimdalUbuntutrusty*
HeimdalUbuntutrusty/esm*
HeimdalUbuntuupstream*
HeimdalUbuntuxenial*
SambaUbuntubionic*
SambaUbuntudevel*
SambaUbuntuesm-infra-legacy/trusty*
SambaUbuntuesm-infra/bionic*
SambaUbuntuesm-infra/focal*
SambaUbuntuesm-infra/xenial*
SambaUbuntufocal*
SambaUbuntujammy*
SambaUbuntukinetic*
SambaUbuntulunar*
SambaUbuntumantic*
SambaUbuntunoble*
SambaUbuntuoracular*
SambaUbuntuplucky*
SambaUbuntuquesting*
SambaUbuntutrusty*
SambaUbuntutrusty/esm*
SambaUbuntuupstream*
SambaUbuntuxenial*

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References