CVE Vulnerabilities

CVE-2023-32324

Heap-based Buffer Overflow

Published: Jun 01, 2023 | Modified: Nov 21, 2024
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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

OpenPrinting CUPS is an open source printing system. In versions 2.4.2 and prior, a heap buffer overflow vulnerability would allow a remote attacker to launch a denial of service (DoS) attack. A buffer overflow vulnerability in the function format_log_line could allow remote attackers to cause a DoS on the affected system. Exploitation of the vulnerability can be triggered when the configuration file cupsd.conf sets the value of loglevel to DEBUG. No known patches or workarounds exist at time of publication.

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

Name Vendor Start Version End Version
Cups Openprinting * 2.4.2 (including)
Cups Ubuntu bionic *
Cups Ubuntu devel *
Cups Ubuntu esm-infra/xenial *
Cups Ubuntu focal *
Cups Ubuntu jammy *
Cups Ubuntu kinetic *
Cups Ubuntu lunar *
Cups Ubuntu trusty *
Cups Ubuntu xenial *
Red Hat Enterprise Linux 8 RedHat cups-1:2.2.6-54.el8_9 *
Red Hat Enterprise Linux 8 RedHat cups-1:2.2.6-54.el8_9 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat cups-1:2.2.6-45.el8_6.4 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat cups-1:2.2.6-51.el8_8.3 *
Red Hat Enterprise Linux 9 RedHat cups-1:2.3.3op2-21.el9 *
Red Hat Enterprise Linux 9 RedHat cups-1:2.3.3op2-21.el9 *

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