Security Research

Security Blog

Page 16

critical8 min

Stack Buffer Overflow in AmigaOS C Code: How strcpy Almost Became a Backdoor

A critical stack buffer overflow vulnerability was discovered and patched in `uae_integration.c`, where an unbounded `strcpy` call allowed attackers to overwrite stack memory and potentially execute arbitrary code. The fix eliminates the unsafe string copy operation, closing a direct path to arbitrary code execution on AmigaOS/AROS systems that lack modern memory protections like stack canaries and ASLR. This case is a timeless reminder that classic C memory safety bugs remain dangerous — especi

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

Critical Buffer Overflow in NES Emulator: How Unbounded memcpy Puts Systems at Risk

A critical buffer overflow vulnerability was discovered and patched in a NES emulator's port abstraction layer, where caller-supplied sizes were passed directly to memcpy without any bounds checking. This systemic flaw affected every supported platform port — SDL3, SDL2, RT-Thread, and the default port — meaning a crafted NES ROM could corrupt heap or stack memory across all targets. The fix introduces proper bounds validation before memory copy operations, closing a dangerous attack vector that

#buffer-overflow#memory-safety#c-programming+4 more
O
orbisai0security
May 11, 2026
critical9 min

Shell Injection in Sphinx Extensions: How a Docs Tool Became a Security Risk

A critical shell injection vulnerability was discovered and fixed in a Sphinx documentation extension (gmtplot.py), where subprocess calls using shell=True allowed arbitrary command execution through crafted filenames in RST documentation files. This fix demonstrates how even documentation tooling can become an attack vector when user-controlled input reaches shell interpreters without sanitization. Understanding and remediating this class of vulnerability is essential for any project that proce

#shell-injection#python#subprocess+4 more
O
orbisai0security
May 11, 2026
critical8 min

Critical Buffer Overflow in matfunc.c: How Unvalidated memcpy Lengths Enable Heap Corruption

A critical buffer overflow vulnerability was discovered and patched in matfunc.c, where three memcpy calls used unvalidated, user-influenced lengths that could write beyond allocated buffer boundaries. If exploited, an attacker supplying maliciously crafted matrix dimensions could corrupt adjacent heap or stack memory, potentially leading to arbitrary code execution. The fix adds proper bounds validation before each copy operation, closing a dangerous attack surface.

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

Heap Buffer Overflow in SSL/TLS: When Proto Length Goes Wrong

A critical heap buffer overflow vulnerability was discovered and patched in `src/ssl.c`, where improper bounds checking during ALPN/NPN protocol list construction could allow an attacker to corrupt heap memory and potentially execute arbitrary code. The fix addresses both the missing capacity validation and a dangerous integer overflow in size arithmetic that could lead to undersized allocations followed by out-of-bounds writes. Understanding this class of vulnerability is essential for any deve

#security#buffer-overflow#ssl+4 more
O
orbisai0security
May 11, 2026
high8 min

Path Traversal in Patch Utilities: How a Missing Validation Let Attackers Write Anywhere

A high-severity path traversal vulnerability (CWE-22) was discovered and fixed in the `patch` utility's input handling code, where filenames derived from diff headers were passed directly to file operations without sanitization. An attacker supplying a crafted patch file could have written arbitrary content to any location on the filesystem — including sensitive system files like `/etc/sudoers` or cron jobs. This post breaks down how the vulnerability works, why it's dangerous, and how to preven

#path-traversal#cwe-22#patch-utility+4 more
O
orbisai0security
May 11, 2026
critical8 min

Critical Buffer Overflow in opencstl.h: How Unchecked memcpy Kills Security

A critical buffer overflow vulnerability was discovered and patched in opencstl.h, where multiple memcpy operations blindly trusted caller-supplied length parameters without verifying destination buffer capacity. Left unpatched, attackers could exploit oversized type strings or manipulated size calculations to corrupt heap memory, potentially achieving remote code execution or privilege escalation. This post breaks down how the vulnerability works, how it was fixed, and what every C/C++ develope

#buffer-overflow#memory-safety#c-cpp+4 more
O
orbisai0security
May 11, 2026
high7 min

Shell Injection via os.system: How Unsanitized Input Becomes a Command Execution Nightmare

A high-severity shell injection vulnerability was discovered and patched in `artbox/romtiles.py`, where unsanitized user-controlled input was passed directly to `os.system()` via an f-string, allowing attackers to execute arbitrary operating system commands. The fix replaces the dangerous `os.system()` calls with the safer `subprocess` module, which properly separates command arguments from user data. This type of vulnerability is a textbook example of why input sanitization and safe API usage a

#security#shell-injection#python+4 more
O
orbisai0security
May 11, 2026
critical10 min

Critical Kernel FAT32 Out-of-Bounds Write: Ring 0 Code Execution

A critical memory corruption vulnerability in a kernel FAT32 filesystem driver allowed attackers to trigger out-of-bounds writes by crafting malicious filesystem images, ultimately enabling arbitrary code execution at the highest privilege level (ring 0). The fix adds proper bounds validation for directory entry indices and cluster offsets parsed from on-disk FAT32 structures, closing a complete privilege escalation chain that could give an attacker full control of the system.

#kernel-security#memory-corruption#fat32+4 more
O
orbisai0security
May 10, 2026
critical8 min

Critical Buffer Overflow in strcpy(): How Unbounded Copies Crash Systems

A critical buffer overflow vulnerability was discovered and patched in a custom `strcpy()` implementation used system-wide across kernel and userspace code. Without bounds checking, any oversized input could overwrite stack frames, return addresses, or heap metadata — opening the door to remote code execution. This post breaks down how the vulnerability works, how it was fixed, and what every C developer should know to avoid the same mistake.

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

Critical Heap Exploitation Chain in trie.c: How Memory Bugs Become Full Compromise

A critical vulnerability chain discovered in `src/trie/trie.c` combines heap buffer overflows and use-after-free bugs into a complete process compromise exploit. By corrupting glibc memory allocator metadata, an attacker could hijack execution flow and achieve arbitrary code execution. This post breaks down how these primitives chain together and what developers can do to prevent similar issues.

#c#memory-safety#heap-exploitation+4 more
O
orbisai0security
May 10, 2026
critical8 min

Stack Buffer Overflow in ODBC Connection Strings: A Critical C Vulnerability Fixed

A critical stack buffer overflow vulnerability was discovered and patched in `src/dbodbc.c`, where unbounded `sprintf` calls allowed attackers to overflow a fixed-size buffer by supplying oversized DSN, UID, or PWD values in ODBC connection strings. Left unpatched, this flaw could enable attackers to overwrite saved return addresses and achieve arbitrary code execution. This post breaks down how the vulnerability works, how it was fixed, and what developers can do to prevent similar issues in th

#c#buffer-overflow#odbc+4 more
O
orbisai0security
May 10, 2026