First published: Sun Aug 11 2013(Updated: )
An out-of buffer bounds write flaw was found in the way the readdir_r function in glibc, the GNU C Library, handled a directory entry whose file name name contained more byte than the NAME_MAX characters constant indicated. An attacker could provide a specially-crafted (local) NTFS or (remote) CIFS file system that, when processed in an application using the readdir_r() function, would cause that application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. Upstream bug report: [1] <a href="http://sourceware.org/bugzilla/show_bug.cgi?id=14699">http://sourceware.org/bugzilla/show_bug.cgi?id=14699</a> Latest patch proposal: [2] <a href="http://sourceware.org/ml/libc-alpha/2013-05/msg00445.html">http://sourceware.org/ml/libc-alpha/2013-05/msg00445.html</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
GNU glibc | <=2.18 | |
GNU glibc | =2.0 | |
GNU glibc | =2.0.1 | |
GNU glibc | =2.0.2 | |
GNU glibc | =2.0.3 | |
GNU glibc | =2.0.4 | |
GNU glibc | =2.0.5 | |
GNU glibc | =2.0.6 | |
GNU glibc | =2.1 | |
GNU glibc | =2.1.1 | |
GNU glibc | =2.1.1.6 | |
GNU glibc | =2.1.2 | |
GNU glibc | =2.1.3 | |
GNU glibc | =2.1.9 | |
GNU glibc | =2.10.1 | |
GNU glibc | =2.11 | |
GNU glibc | =2.11.1 | |
GNU glibc | =2.11.2 | |
GNU glibc | =2.11.3 | |
GNU glibc | =2.12.1 | |
GNU glibc | =2.12.2 | |
GNU glibc | =2.13 | |
GNU glibc | =2.14 | |
GNU glibc | =2.14.1 | |
GNU glibc | =2.15 | |
GNU glibc | =2.16 | |
GNU glibc | =2.17 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.