CVE-2026-133307 in ClassiCubeinfo

Summary

by MITRE • 11/20/2026

ClassiCube before 1.4.0 contains a heap-based out-of-bounds write vulnerability in Png_Decode in src/Bitmap.c that allows malicious servers to corrupt client memory by sending a PNG with a duplicate IHDR chunk. Attackers can supply crafted PNGs via texture pack URLs or player skins so the unreset bufferIdx underflows remaining space, letting IDAT data overflow the buffer to crash clients or execute code.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in ClassiCube versions prior to 1.4.0 represents a critical heap-based out-of-bounds write flaw located within the PNG decoding logic of the Bitmap module. This security defect arises from an insufficient validation mechanism when processing Portable Network Graphics files, specifically targeting the handling of Image Header IHDR chunks during the decompression process. The root cause lies in the failure to properly reset or validate internal buffer indices after encountering duplicate or malformed structural elements within the image file structure. When a malicious actor supplies a crafted PNG containing multiple IHDR chunks, the decoder fails to account for this anomaly correctly, leading to an underflow of the buffer index variable known as bufferIdx. This miscalculation results in the application misinterpreting the available space remaining in the allocated heap memory region designated for storing decoded pixel data.

From a technical perspective, the exploitation vector relies on the interaction between the PNG parser and the underlying C-based memory management routines used by ClassiCube to render textures and player skins. The game engine allows users to load custom assets via texture pack URLs or through multiplayer server connections where players can define their own skin appearances. By embedding a specially constructed PNG file within these vectors, an attacker can trigger the flawed logic in Png_Decode. As the decoder processes the IDAT data chunks following the malformed header sequence, it writes pixel information into memory locations that have already been processed or are outside the bounds of the intended buffer allocation due to the underflowed index state. This condition effectively allows for arbitrary write operations on the heap, bypassing standard boundary checks that should prevent such overflows.

The operational impact of this vulnerability is severe, encompassing both denial of service and potential remote code execution scenarios. In its most immediate manifestation, the memory corruption causes instability within the game client, leading to application crashes or freezes when a user loads the malicious asset. However, given the nature of heap-based buffer overflows in C/C++ applications, this flaw presents a significant risk for arbitrary code execution. An attacker with sufficient skill can leverage specific heap layout techniques and gadget chains to overwrite function pointers or object metadata within adjacent memory structures. This capability allows for the injection and subsequent execution of malicious shellcode on the victim's machine, effectively compromising the integrity and confidentiality of the user system through what is ostensibly a benign media file loading mechanism.

This vulnerability aligns with Common Weakness Enumeration standard CWE-120, which describes buffer copy without checking size limits, specifically manifesting here as an out-of-bounds write due to incorrect index management. Furthermore, from a tactical standpoint related to the MITRE ATT&CK framework, this flaw facilitates initial access and execution phases by allowing adversaries to deliver malicious payloads disguised as standard game assets. The attack path involves social engineering or server-side manipulation where victims are induced to load compromised textures or skins, demonstrating how client-side rendering engines can become vectors for system compromise if input validation is not rigorously enforced.

Mitigation strategies must prioritize immediate patching of the ClassiCube installation to version 1.4.0 or later, which addresses this specific logic error in the Bitmap decoding routine. For environments where upgrading is not immediately feasible, network-level controls should be implemented to restrict texture pack URLs and player skin sources to trusted domains only. Additionally, implementing strict input validation on all external image data before it reaches the decoder would prevent malformed structures from triggering the underflow condition. Security teams should also monitor for unusual memory allocation patterns or crashes associated with PNG processing modules as an indicator of attempted exploitation in real-time environments.

Responsible

VulnCheck

Reservation

11/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00428

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!