[BACK]Return to errata24.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/errata24.html between version 1.83 and 1.84

version 1.83, 2019/05/27 22:55:19 version 1.84, 2019/05/28 16:32:41
Line 84 
Line 84 
 <hr>  <hr>
   
 <ul>  <ul>
   
 <li id="bmap">  <li id="bmap">
 <strong>RELIABILITY FIX</strong>  <strong>001: RELIABILITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A local user can crash the system by reading a file larger than 64meg  A local user can crash the system by reading a file larger than 64meg
 from an ext2fs partition.  from an ext2fs partition.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/bmap.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/bmap.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="lnpanic">  <li id="lnpanic">
 <strong>RELIABILITY FIX</strong>  <strong>002: RELIABILITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A local user can crash the system because of a bug in the vfs layer.  A local user can crash the system because of a bug in the vfs layer.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/lnpanic.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/lnpanic.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="poll">  <li id="poll">
 <strong>SECURITY FIX</strong>  <strong>003: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A machine crash is possible when playing with poll(2).  A machine crash is possible when playing with poll(2).
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/poll.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/poll.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="nlink">  <li id="nlink">
 <strong>SECURITY FIX</strong>  <strong>004: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A machine crash is possible when playing with link(2) on FFS.  A machine crash is possible when playing with link(2) on FFS.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nlink.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nlink.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 This is version four of the patch.  This is version four of the patch.
 <p>  <p>
   
 <li id="ping">  <li id="ping">
 <strong>SECURITY FIX</strong>  <strong>005: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A buffer overflow existed in ping(8), which may have a security issue.  A buffer overflow existed in ping(8), which may have a security issue.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/ping.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/ping.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="ipqrace">  <li id="ipqrace">
 <strong>SECURITY FIX</strong>  <strong>006: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A race condition in IP ipq handling could permit a remote crash.  A race condition in IP ipq handling could permit a remote crash.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/ipqrace.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/ipqrace.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
   <br>
 It must be installed after <a href="errata24.html#maxqueue">the maxqueue patch</a>.  It must be installed after <a href="errata24.html#maxqueue">the maxqueue patch</a>.
 and <a href="errata24.html#tcpfix">the tcp decoding patch</a>.  and <a href="errata24.html#tcpfix">the tcp decoding patch</a>.
 <p>  <p>
   
 <li id="accept">  <li id="accept">
 <strong>SECURITY FIX</strong>  <strong>007: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A race condition existed between accept(2) and select(2) which could  A race condition existed between accept(2) and select(2) which could
 permit an attacker to hang sockets from remote.  permit an attacker to hang sockets from remote.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/accept.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/accept.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="maxqueue">  <li id="maxqueue">
 <strong>SECURITY FIX</strong>  <strong>008: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 IP fragment assembly can bog the machine excessively and cause problems.  IP fragment assembly can bog the machine excessively and cause problems.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/maxqueue.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/maxqueue.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="uio">  <li id="uio">
 <strong>FUNCTIONALITY FIX</strong>  <strong>009: FUNCTIONALITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The readv(2) and writev(2) system calls would not accept a <em>struct iovec</em>  The readv(2) and writev(2) system calls would not accept a <em>struct iovec</em>
 with an <b>iov_len</b> of 0.  This causes a db test in perl to fail.  with an <b>iov_len</b> of 0.  This causes a db test in perl to fail.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/uio.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/uio.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="rst">  <li id="rst">
 <strong>SECURITY FIX</strong>  <strong>010: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 TCP/IP RST handling was too sloppy.  TCP/IP RST handling was too sloppy.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/rst.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/rst.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="kvm_mkdb">  <li id="kvm_mkdb">
 <strong>FUNCTIONALITY FIX</strong>  <strong>011: FUNCTIONALITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 During bootup, kvm_mkdb may exit with the error "kvm_mkdb: cannot allocate  During bootup, kvm_mkdb may exit with the error "kvm_mkdb: cannot allocate
 memory".  memory".
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/kvm_mkdb.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/kvm_mkdb.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="nfs3_solaris7">  <li id="nfs3_solaris7">
 <strong>FUNCTIONALITY FIX</strong>  <strong>012: FUNCTIONALITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A problem with writing to NFS version 3 mounted filesystems from Solaris 7  A problem with writing to NFS version 3 mounted filesystems from Solaris 7
 hosts exists.  Attempts to create files will result in an error such as  hosts exists.  Attempts to create files will result in an error such as
 "Inappropriate file type or format".  "Inappropriate file type or format".
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nfs3_solaris7.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nfs3_solaris7.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="nfs3">  <li id="nfs3">
 <strong>FUNCTIONALITY FIX</strong>  <strong>013: FUNCTIONALITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A problem with NFS version 3 mounts on big endian machines (m68k, sparc  A problem with NFS version 3 mounts on big endian machines (m68k, sparc
 and powerpc) exists when mounting filesystems larger than 2gig.  You  and powerpc) exists when mounting filesystems larger than 2gig.  You
 can see evidence of the bug by running df(1) and checking for negative  can see evidence of the bug by running df(1) and checking for negative
 partition sizes.  partition sizes.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nfs3.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nfs3.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="termcap">  <li id="termcap">
 <strong>SECURITY FIX</strong>  <strong>014: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A security problem exists in the curses and ocurses libraries that affect  A security problem exists in the curses and ocurses libraries that affect
 setuid programs linked with -lcurses or -locurses.  setuid programs linked with -lcurses or -locurses.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/termcap.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/termcap.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <br>  <br>
 Precompiled versions of libcurses and libocurses exist for the  Precompiled versions of libcurses and libocurses exist for the
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/curses.tar.gz">i386</a>  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/curses.tar.gz">i386</a>
 platform.  Unpack it in /usr/lib.  platform.  Unpack it in /usr/lib.
 <p>  <p>
   
 <li id="terminfo">  <li id="terminfo">
 <strong>FUNCTIONALITY FIX</strong>  <strong>015: FUNCTIONALITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A workaround for an xterm problem that causes <b>vi</b> to not  A workaround for an xterm problem that causes <b>vi</b> to not
 restore the correct cursor position on exit.  restore the correct cursor position on exit.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/terminfo.src.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/terminfo.src.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <br>  <br>
Line 215 
Line 247 
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/terminfo.db-BE.tar.gz">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/terminfo.db-BE.tar.gz">
 big endian</a> version.  big endian</a> version.
 <p>  <p>
   
 <li id="userdir">  <li id="userdir">
 <strong>FUNCTIONALITY FIX</strong>  <strong>016: FUNCTIONALITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 <b>userdir</b> support was accidentally left out of httpd(8).  <b>userdir</b> support was accidentally left out of httpd(8).
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/userdir.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/userdir.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="bootpd">  <li id="bootpd">
 <strong>SECURITY FIX</strong>  <strong>017: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A remotely exploitable problem exists in bootpd(8).  bootpd is disabled  A remotely exploitable problem exists in bootpd(8).  bootpd is disabled
 by default, but some people may actually be using it.  by default, but some people may actually be using it.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/bootpd.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/bootpd.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 This is the second version of the patch.  This is the second version of the patch.
 <p>  <p>
   
 <li id="tcpfix">  <li id="tcpfix">
 <strong>SECURITY FIX</strong>  <strong>018: SECURITY FIX</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A remote machine lockup problem exists in the TCP decoding code.  A remote machine lockup problem exists in the TCP decoding code.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/tcpfix.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/tcpfix.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="tss">  <li id="tss">
 <strong>SECURITY FIX</strong><br>  <strong>019: SECURITY FIX</strong><br>
 This is another fix for a kernel crash caused by the  This is another fix for a kernel crash caused by the
 <b>crashme</b> program.  <b>crashme</b> program.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/tss.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/tss.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="bootargv">  <li id="bootargv">
 <strong>FUNCTIONALITY FIX</strong><br>  <strong>020: FUNCTIONALITY FIX</strong><br>
 The kernel was using a fixed and hard-coded location for the arguments  The kernel was using a fixed and hard-coded location for the arguments
 vector passed from the <b>/boot</b> loader.  This prevented  vector passed from the <b>/boot</b> loader.  This prevented
 <b>/boot</b> from placing the boot arguments vector at any  <b>/boot</b> from placing the boot arguments vector at any
Line 254 
Line 295 
 stage.  In 2.5, the bootblocks will be modified to use a new location.  stage.  In 2.5, the bootblocks will be modified to use a new location.
 Hence, if you wish old kernels to boot on a new bootblock, those  Hence, if you wish old kernels to boot on a new bootblock, those
 kernels will only work if they were linked with this patch.  kernels will only work if they were linked with this patch.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/bootargv.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/bootargv.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="trctrap">  <li id="trctrap">
 <strong>SECURITY FIX</strong><br>  <strong>021: SECURITY FIX</strong><br>
 i386 trace-trap handling when DDB was configured could cause a system  i386 trace-trap handling when DDB was configured could cause a system
 crash.  crash.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/trctrap.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/trctrap.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="installboot">  <li id="installboot">
 <strong>FUNCTIONALITY FIX</strong><br>  <strong>022: FUNCTIONALITY FIX</strong><br>
 i386 installboot had a sign extension bug which prevented proper bootblock  i386 installboot had a sign extension bug which prevented proper bootblock
 initialization when the root filesystem was placed beyond 4GB.  initialization when the root filesystem was placed beyond 4GB.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/installboot.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/installboot.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 Unfortunately, updated 2.4 install floppies are not available.  Just ensure  Unfortunately, updated 2.4 install floppies are not available.  Just ensure
 that your root filesystem is below 4GB, for now.  that your root filesystem is below 4GB, for now.
 <p>  <p>
   
 <li id="hme">  <li id="hme">
 <strong>DRIVER FIX</strong><br>  <strong>023: DRIVER FIX</strong><br>
 The sparc hme(4) and be(4) drivers work poorly on some types of SS-20  The sparc hme(4) and be(4) drivers work poorly on some types of SS-20
 machines.  This is because those machines lie, saying they support 64-bit DMA  machines.  This is because those machines lie, saying they support 64-bit DMA
 bursting.  No sun4m machines support that.  bursting.  No sun4m machines support that.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/sparc/hme.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/sparc/hme.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="le">  <li id="le">
 <strong>DRIVER FIX</strong><br>  <strong>024: DRIVER FIX</strong><br>
 The sparc le(4) driver does media changes incorrectly on one type of  The sparc le(4) driver does media changes incorrectly on one type of
 sbus le(4) card.  sbus le(4) card.
   <br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/sparc/le.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.4/sparc/le.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
   
 <li id="hp300X">  <li id="hp300X">
 <strong>FUNCTIONALITY FIX</strong><br>  <strong>025: FUNCTIONALITY FIX</strong><br>
 The Xhp as shipped does not have the execute permissions set.  The fix is  The Xhp as shipped does not have the execute permissions set.  The fix is
 'chmod 755 /usr/X11R6/bin/Xhp' if you have installed X.  'chmod 755 /usr/X11R6/bin/Xhp' if you have installed X.
 <p>  <p>
Legend:
Removed from v.1.83  
changed lines
  Added in v.1.84