oss-sec mailing list archives
Re: hardlink(1) has buffer overflows, is unsafe on changing trees
From: Huzaifa Sidhpurwala <huzaifas () redhat com>
Date: Fri, 21 Oct 2011 15:29:41 +0530
On 10/20/2011 08:27 PM, Josh Bressers wrote:
The hardlink(1) program from Fedora is susceptible to buffer overflows of fixed-size nambuf1 and nambuf2 buffers when run on a tree with deeply nested directories and/or with long directory or file names. I was able to reproduce the problem (got a segfault) by running the program on a directory containing 20 nested directories with 250-character names.CVE-2011-3630 hardlink buffer overflows https://bugzilla.redhat.com/show_bug.cgi?id=746709
FORTIFY_SOURCE should really be able to catch this buffer overflow.The buffer being overflown here in in BSS, But strcat() is used to append to this buffer and __builtin___strcat_chk catches it, resulting in the program being terminated.
Nice one though! -- Huzaifa Sidhpurwala / Red Hat Security Response Team
Current thread:
- hardlink(1) has buffer overflows, is unsafe on changing trees Solar Designer (Oct 15)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Josh Bressers (Oct 20)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Huzaifa Sidhpurwala (Oct 21)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Solar Designer (Oct 21)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Solar Designer (Oct 21)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Solar Designer (Oct 21)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Huzaifa Sidhpurwala (Oct 23)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Huzaifa Sidhpurwala (Oct 21)
- Re: hardlink(1) has buffer overflows, is unsafe on changing trees Josh Bressers (Oct 20)