Security Research

Security Blog

Page 7

critical8 min

Heap Out-of-Bounds Read in GLTF Loader: How a Missing Bounds Check Could Crash Your App or Leak Memory

A critical out-of-bounds heap read vulnerability was discovered in the Effekseer GLTF resource loader, where a `memcpy` operation copied data from a buffer without first verifying the source contained enough bytes. An attacker could craft a malicious GLTF file with truncated buffer data to crash the application or leak sensitive heap memory contents. The fix adds a simple but essential bounds check before the copy operation, ensuring the source buffer always contains at least as many bytes as th

#cpp#memory-safety#buffer-overflow+4 more
O
orbisai0security
May 27, 2026
critical8 min

Critical Buffer Overflow Fixed: sprintf() to snprintf() in Vorbis Producer

A critical buffer overflow vulnerability was discovered in the Vorbis producer module (`src/modules/vorbis/producer_vorbis.c`), where an unchecked `sprintf()` call allowed attacker-controlled metadata from Vorbis audio files to overflow a fixed-size buffer. The fix replaces `sprintf()` with `snprintf()` and adds explicit bounds checking, ensuring that no metadata key — no matter how long or maliciously crafted — can corrupt adjacent memory. This class of vulnerability is one of the oldest and mo

#buffer-overflow#c-security#media-parsing+4 more
O
orbisai0security
May 27, 2026
high7 min

CVE-2026-41676: Fixing a High-Severity OpenSSL Vulnerability in Rust Applications

CVE-2026-41676 is a high-severity vulnerability discovered in the rust-openssl crate, which provides OpenSSL bindings for Rust applications. Left unpatched, this flaw could expose backend services to cryptographic or memory-safety attacks through the underlying OpenSSL layer. The fix involved upgrading the rust-openssl dependency from version 0.10.75 to 0.10.78 in the project's Cargo.toml and Cargo.lock files.

#rust#openssl#cve+4 more
O
orbisai0security
May 26, 2026
critical8 min

Critical Stack Buffer Overflow in console.c: How strcat Without Bounds Checking Enables Arbitrary Code Execution

A critical stack buffer overflow vulnerability was discovered and patched in `binding/shared/console.c`, where an unchecked `strcat()` call concatenating file path components into a fixed-size stack buffer could allow attackers to overwrite the return address and achieve arbitrary code execution. This class of vulnerability — CWE-120, also known as a "Classic Buffer Overflow" — is one of the oldest and most dangerous bugs in systems programming, and its presence in a shared binding layer makes i

#buffer-overflow#C#CWE-120+4 more
O
orbisai0security
May 26, 2026
critical8 min

Critical Buffer Overflow in ELF Parser: How a Missing Bounds Check Almost Became a Heap Exploit

A critical out-of-bounds memory vulnerability was discovered and patched in `utils/symbol-rawelf.c`, where two separate `memcpy` calls lacked proper bounds validation when processing ELF binary files. Without these checks, a maliciously crafted ELF file could trigger an out-of-bounds read or heap overflow, potentially leading to remote code execution or memory corruption. This post breaks down how the vulnerability works, how it was fixed, and what every C developer should know about safe memory

#security#buffer-overflow#c-programming+4 more
O
orbisai0security
May 25, 2026
critical9 min

Critical Use-After-Free: The Dangerous krealloc() Pattern in Linux Kernel Code

A critical memory safety vulnerability was discovered and fixed in the Linux kernel's SSDFS filesystem driver, where directly assigning the return value of krealloc() to the original pointer could cause use-after-free conditions or NULL pointer dereferences when memory allocation fails. This well-known dangerous pattern, explicitly warned against in Linux kernel coding guidelines, could allow attackers to trigger memory corruption under low-memory conditions. The fix implements the safe temporar

#linux-kernel#memory-safety#use-after-free+4 more
O
orbisai0security
May 25, 2026
critical9 min

Critical Buffer Overflow in hooker.c: How a Missing Bounds Check Could Crash Your System

A critical buffer overflow vulnerability was discovered and patched in hooker.c, where a memcpy call at line 1228 copied instruction bytes into a fixed-size bridge buffer without validating the copy length. An attacker or crafted binary could exploit this to corrupt memory, crash the process, or potentially achieve arbitrary code execution. The fix adds a simple but essential bounds check before the copy operation, enforcing the invariant that save_bytes never exceeds the allocated bridge buffer

#buffer-overflow#c-security#memory-safety+4 more
O
orbisai0security
May 25, 2026
medium9 min

DMA Bounds Overflow: How a Missing Validation Nearly Opened a Host Memory Escape

A medium-severity vulnerability in `src/ddma.c` allowed a malicious guest OS to program DMA controllers with unconstrained transfer sizes and addresses, potentially enabling guest-to-host memory access in an emulated environment. The fix introduces strict bounds validation to ensure all DMA transfers stay within allocated memory regions, closing a dangerous path to host memory disclosure and corruption.

#security#emulation#dma+4 more
O
orbisai0security
May 24, 2026
critical8 min

Buffer Overflow via Crafted SCSI Commands: How a Missing Bounds Check Almost Bricked Your ESP32

A critical out-of-bounds memory access vulnerability was discovered in the FatFSUSB library used by the micro-journal ESP32 firmware, where memcpy operations on a sector buffer accepted attacker-controlled offset and size values from USB SCSI commands without any bounds validation. A malicious USB host could craft SCSI READ/WRITE commands to corrupt memory, potentially crashing the device or executing arbitrary code. The fix adds a simple but essential bounds check before every memcpy operation,

#buffer-overflow#embedded-security#esp32+4 more
O
orbisai0security
May 24, 2026
critical8 min

Heap Buffer Overflow in kiss_fft: How Integer Overflow Kills Memory Safety

A high-severity heap buffer overflow vulnerability was discovered and patched in the kiss_fft audio processing library, where integer overflow in allocation size calculations could allow attackers to trigger memory corruption via crafted audio file metadata. The fix adds bounds checking before memory allocation, preventing adversarial `nfft` values from causing undersized heap allocations followed by catastrophic buffer overflows. This class of vulnerability is a reminder that untrusted input mu

#security#c#memory-safety+4 more
O
orbisai0security
May 24, 2026
critical10 min

Critical Buffer Overflow in UTF-8 Validation: How Unchecked memcpy Enables Arbitrary Code Execution

A critical buffer overflow vulnerability was discovered and patched in third-party UTF-8 validation code, where multiple unchecked `memcpy` operations could allow attackers to write beyond buffer boundaries, corrupt heap metadata, and potentially execute arbitrary code. This fix highlights a timeless lesson in C programming: never trust that your source data fits in your destination buffer. The patch affects `lemire-avx2.c`, `lemire-sse.c`, and `main.c` — three files that together form the backb

#buffer-overflow#c-security#memory-safety+4 more
O
orbisai0security
May 24, 2026
critical10 min

Critical Buffer Overflow in UPnP TV Device: How strcpy Almost Broke Your Network

A critical buffer overflow vulnerability was discovered in the UPnP TV device sample code (`tv_device.c`), where unchecked `strcpy` calls allowed network-adjacent attackers to overflow fixed-size buffers with crafted UPnP discovery strings. The fix replaces unbounded string copies with length-checked alternatives (`strlcpy`/`snprintf`), closing a classic CWE-120 attack vector that required zero authentication to exploit.

#buffer-overflow#c-security#upnp+4 more
O
orbisai0security
May 24, 2026