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

Diff for /www/errata24.html between version 1.64 and 1.65

version 1.64, 2014/10/02 14:34:45 version 1.65, 2015/02/14 04:36:51
Line 81 
Line 81 
 <hr>  <hr>
   
 <ul>  <ul>
 <li><a name="bmap"></a>  <li id="bmap">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font>  <font color="#009000"><strong>RELIABILITY FIX</strong></font>
 &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
Line 89 
Line 89 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/bmap.patch">  <a href="http://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><a name="lnpanic"></a>  <li id="lnpanic">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font>  <font color="#009000"><strong>RELIABILITY FIX</strong></font>
 &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.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/lnpanic.patch">  <a href="http://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><a name="poll"></a>  <li id="poll">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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).
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/poll.patch">  <a href="http://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><a name="nlink"></a>  <li id="nlink">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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.
Line 111 
Line 111 
 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><a name="ping"></a>  <li id="ping">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/ping.patch">  <a href="http://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><a name="ipqrace"></a>  <li id="ipqrace">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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.
Line 127 
Line 127 
 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><a name="accept"></a>  <li id="accept">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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
Line 135 
Line 135 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/accept.patch">  <a href="http://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><a name="maxqueue"></a>  <li id="maxqueue">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/maxqueue.patch">  <a href="http://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><a name="uio"></a>  <li id="uio">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>
 &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>
Line 150 
Line 150 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/uio.patch">  <a href="http://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><a name="rst"></a>  <li id="rst">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/rst.patch">  <a href="http://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><a name="kvm_mkdb"></a>  <li id="kvm_mkdb">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>
 &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
Line 165 
Line 165 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/kvm_mkdb.patch">  <a href="http://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><a name="nfs3_solaris7"></a>  <li id="nfs3_solaris7">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>
 &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
Line 174 
Line 174 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nfs3_solaris7.patch">  <a href="http://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><a name="nfs3"></a>  <li id="nfs3">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>
 &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
Line 184 
Line 184 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nfs3.patch">  <a href="http://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><a name="termcap"></a>  <li id="termcap">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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
Line 196 
Line 196 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/curses.tar.gz">i386</a>  <a href="http://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><a name="terminfo"></a>  <li id="terminfo">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A workaround for an xterm problem that causes <strong>vi</strong> to not  A workaround for an xterm problem that causes <strong>vi</strong> to not
Line 212 
Line 212 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/terminfo.db-BE.tar.gz">  <a href="http://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><a name="userdir"></a>  <li id="userdir">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 <strong>userdir</strong> support was accidentally left out of httpd(8).  <strong>userdir</strong> support was accidentally left out of httpd(8).
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/userdir.patch">  <a href="http://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><a name="bootpd"></a>  <li id="bootpd">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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
Line 228 
Line 228 
 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><a name="tcpfix"></a>  <li id="tcpfix">
 <font color="#009000"><strong>SECURITY FIX</strong></font>  <font color="#009000"><strong>SECURITY FIX</strong></font>
 &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.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/tcpfix.patch">  <a href="http://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><a name="tss"></a>  <li id="tss">
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font><br>
 This is another fix for a kernel crash caused by the  This is another fix for a kernel crash caused by the
 <strong>crashme</strong> program.  <strong>crashme</strong> program.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/tss.patch">  <a href="http://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><a name="bootargv"></a>  <li id="bootargv">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><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 <strong>/boot</strong> loader.  This prevented  vector passed from the <strong>/boot</strong> loader.  This prevented
Line 254 
Line 254 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/bootargv.patch">  <a href="http://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><a name="trctrap"></a>  <li id="trctrap">
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font><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.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/i386/trctrap.patch">  <a href="http://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><a name="installboot"></a>  <li id="installboot">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><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.
Line 270 
Line 270 
 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><a name="hme"></a>  <li id="hme">
 <font color="#009000"><strong>DRIVER FIX</strong></font><br>  <font color="#009000"><strong>DRIVER FIX</strong></font><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
Line 278 
Line 278 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/sparc/hme.patch">  <a href="http://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><a name="le"></a>  <li id="le">
 <font color="#009000"><strong>DRIVER FIX</strong></font><br>  <font color="#009000"><strong>DRIVER FIX</strong></font><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.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/sparc/le.patch">  <a href="http://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><a name="hp300X"></a>  <li id="hp300X">
 <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>  <font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><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.
Legend:
Removed from v.1.64  
changed lines
  Added in v.1.65