See how mcrypt compares to other vendors in security performance
Memory leak in libmcrypt before 2.5.5 allows attackers to cause a denial of service (memory exhaustion) via a large number of requests to the application, which causes libmcrypt to dynamically load algorithms via libtool.
Multiple buffer overflows in libmcrypt before 2.5.5 allow attackers to cause a denial of service (crash).
Created attachment 629285 [details] patch to fix the buffer overflow
Description of problem: A buffer overflow in mcrypt version 2.6.8 and earlier due to long filenames. If a user were tricked into attempting to encrypt/decrypt specially crafted long filename(s), 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 are currently no upstream patches for this flaw.
Version-Release number of selected component (if applicable): mcrypt-2.6.8-9.el6 (possibly others too).
How reproducible: Run mcrypt with ~128 byte long file names.
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
Multiple format string vulnerabilities in mcrypt 2.6.8 and earlier might allow user-assisted remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via vectors involving (1) errors.c or (2) mcrypt.c.
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