snprintf(buffer, sizeof(buffer) - 1, "%s", network_path); buffer[sizeof(buffer)-1] = '\0'; Red Hat’s compiler flags for Anaconda had omitted frame pointers for performance, making debugging and stack protection harder. The patch re-enabled frame pointers to allow better stack integrity. 3. Introduction of Stack Canary Emulation (Pre-StackGuard) Since modern GCC StackGuard didn’t exist in 1997, Red Hat backported a simple canary value check into the Anaconda binary by patching the assembly output directly—a rare and heroic act of manual binary patching.
Unlike today’s streamlined installers, the 1997 Anaconda ran as root with high privileges to partition disks, format filesystems, and copy system libraries. It included a rescue mode and a network installation feature that relied on legacy protocols (FTP, NFS, and HTTP/0.9). The anaconda1997 binary was a statically linked executable that ran before the security framework (like SELinux) existed. The anaconda1997 vulnerability—tracked as CVE-1999-0002 (or sometimes misidentified in underground forums as "anaconda boost overflow")—existed in the network stage 2 loader. When Anaconda prompted the user for a network installation path (e.g., nfs://server/path ), it copied user input into a fixed-size stack buffer of 256 bytes using strcpy() without any bounds checking. anaconda1997 patched
Even if your system is patched, the mindset of the anaconda1997 era—assume boot-time code is vulnerable—must remain. Verify your installer media, use signed images, and always apply the patch. Have a legacy Red Hat 5.0 system? Share your story below. For further reading, see the original Red Hat bug report #1997-1210 and CVE-1999-0002. The anaconda1997 binary was a statically linked executable