OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: horcy (apehaar_at_text-only.demon.nl)
Date: Wed Jan 08 2003 - 10:25:20 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    II. Problem Description

    A programming error in the fpathconf system call can result in the
    given file descriptor's reference count being erroneously incremented.

    A similar problem exists in the developer preview versions of FreeBSD
    5.0, affecting the lseek(2), dup(2), and other system calls.

    III. Impact

    A local attacker may cause the operating system to crash by repeatedly
    calling fpathconf on a file descriptor until the reference count wraps
    to a negative value, and then calling close on that file descriptor.

    Similarly, it may be possible to cause a file descriptor to reference
    unallocated kernel memory, but remain valid. If a new file is later
    opened and the kernel allocates the new file structure at the same
    memory location, then an attacker may be able to gain read or write
    access to that file. This may in turn lead to privilege escalation.

    IV. Workaround

    There is no workaround.

    V. Solution

    The following patch has been verified to apply to FreeBSD 4.4, 4.5,
    4.6, and 4.7 systems.

    a) Download the relevant patch from the location below, and verify the
    detached PGP signature using your PGP utility.

    # fetch
    ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-02:44/filedesc.patch
    # fetch
    ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-02:44/filedesc.patch.asc

    b) Apply the patch.

    # cd /usr/src
    # patch < /path/to/patch

    c) Recompile your kernel as described in
    <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the
    system.

    The question:

    If I periodicly upgrade with cvsup stable and compile kernel it's will fix
    that problem, or I must patch only. does cvsup will replace all of
    source?
    ---------------------------
    Answer:

    if you cvsup to stable it will fix it and of course the patch will fix it.
    But you still have to recompile you kernel, so to if it was time for your
    cvsup stable then i sould suggest you do that. Both will take some time.
    So i would go for the cvsup.

    l8r

    horcy

    --
    budsz
    

    To Unsubscribe: send mail to majordomoFreeBSD.org with "unsubscribe freebsd-security" in the body of the message

    To Unsubscribe: send mail to majordomoFreeBSD.org with "unsubscribe freebsd-security" in the body of the message