CVE-2012-4409: Buffer Overflow
A buffer overflow was reported [1],[2] in mcrypt version 2.6.8 and earlier due to a boundary error in the processing of an encrypted file (via the checkfilehead() function in src/extra.c). If a user were tricked into attempting to decrypt a specially-crafted .nc encrypted flie, this flaw would cause a stack-based buffer overflow that could potentially lead to arbitrary code execution.
Note that this is caught by FORTIFYSOURCE, which renders this to being a crash-only bug on Fedora.
There is currently no upstream patches for this flaw.
[1] https://secunia.com/advisories/50507/ [2] https://bugs.gentoo.org/showbug.cgi?id=434112
Other sources
Stack-based buffer overflow in the checkfilehead function in extra.c in mcrypt 2.6.8 and earlier allows user-assisted remote attackers to execute arbitrary code via an encrypted file with a crafted header containing long salt data that is not properly handled during decryption.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-4409?
CVE-2012-4409 is classified as a high severity vulnerability due to its potential to cause a buffer overflow leading to application crashes or remote code execution.
How do I fix CVE-2012-4409?
To mitigate CVE-2012-4409, you should upgrade to mcrypt version 2.6.9 or later, where the vulnerability has been patched.
What versions are affected by CVE-2012-4409?
CVE-2012-4409 affects mcrypt versions 2.6.8 and earlier, specifically 2.6.4 through 2.6.8.
What are the potential consequences of exploiting CVE-2012-4409?
Exploitation of CVE-2012-4409 could allow an attacker to execute arbitrary code on the victim's machine, potentially leading to data compromise.
How does CVE-2012-4409 occur?
CVE-2012-4409 occurs due to a buffer overflow vulnerability in the check_file_head() function, which mishandles encrypted files.