CVE-2023-52356

A segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. This flaw allows a remote attacker to cause a heap-buffer overflow, leading to a denial of service.

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
Libtiff	Libtiff	- (including)	- (including)
Red Hat Enterprise Linux 8	RedHat	libtiff-0:4.0.9-32.el8_10	*
Red Hat Enterprise Linux 9	RedHat	libtiff-0:4.4.0-15.el9	*
Red Hat AI Inference Server 3.2	RedHat	rhaiis/vllm-cuda-rhel9:sha256:ec961e5acfde5c1ad0a7e0e2c86a0bf56b9bc46357fa124f9db6dff1006076ab	*
Red Hat AI Inference Server 3.2	RedHat	rhaiis/vllm-rocm-rhel9:sha256:7856bdb7ae0d643a7b9362c164d4d4fe3c0c7186f5fff73a7ae9835b3df52e57	*
Red Hat AI Inference Server 3.2	RedHat	rhaiis/model-opt-cuda-rhel9:sha256:dce6b0ea03379bf06664a5200af8b5f5ae3fad13cdce6d21873843f22554800b	*
Red Hat Discovery 2	RedHat	discovery/discovery-ui-rhel9:sha256:310df392f638ef6eca1a26db024ae2cb617db5932f886d2acddc92fb7289e740	*
Gdal	Ubuntu	trusty	*
Gdal	Ubuntu	trusty/esm	*
Gdal	Ubuntu	xenial	*
Qtwebengine-opensource-src	Ubuntu	bionic	*
Qtwebengine-opensource-src	Ubuntu	focal	*
Qtwebengine-opensource-src	Ubuntu	mantic	*
Qtwebengine-opensource-src	Ubuntu	oracular	*
Texmaker	Ubuntu	bionic	*
Texmaker	Ubuntu	focal	*
Texmaker	Ubuntu	mantic	*
Texmaker	Ubuntu	oracular	*
Tiff	Ubuntu	bionic	*
Tiff	Ubuntu	devel	*
Tiff	Ubuntu	esm-infra-legacy/trusty	*
Tiff	Ubuntu	esm-infra/bionic	*
Tiff	Ubuntu	esm-infra/focal	*
Tiff	Ubuntu	esm-infra/xenial	*
Tiff	Ubuntu	focal	*
Tiff	Ubuntu	jammy	*
Tiff	Ubuntu	mantic	*
Tiff	Ubuntu	noble	*
Tiff	Ubuntu	oracular	*
Tiff	Ubuntu	plucky	*
Tiff	Ubuntu	questing	*
Tiff	Ubuntu	trusty	*
Tiff	Ubuntu	trusty/esm	*
Tiff	Ubuntu	xenial	*

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].

https://cwe.mitre.org/data/definitions/92.html

NVD	https://nvd.nist.gov/vuln/detail/CVE-2023-52356
CWE	https://cwe.mitre.org/data/definitions/122.html

Heap-based Buffer Overflow

Weakness

Affected Software

Potential Mitigations

References

CVE-2023-52356

Heap-based Buffer Overflow

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References