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

Diff for /www/errata23.html between version 1.66 and 1.67

version 1.66, 2014/10/02 14:34:45 version 1.67, 2015/02/14 04:36:51
Line 81 
Line 81 
 <hr>  <hr>
   
 <ul>  <ul>
 <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 90 
Line 90 
 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.3/common/tcpfix.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/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="atapi"></a>  <li id="atapi">
 <font color="#009000"><strong>HARDWARE SUPPORT</strong></font>  <font color="#009000"><strong>HARDWARE SUPPORT</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Some ATAPI cdroms which do not support the full mandatory command set,  Some ATAPI cdroms which do not support the full mandatory command set,
Line 106 
Line 106 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <li><a name="chpass"></a>  <li id="chpass">
 <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>
 Chpass(1) has a file descriptor leak which allows an  Chpass(1) has a file descriptor leak which allows an
Line 114 
Line 114 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.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="resid"></a>  <li id="resid">
 <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>
 Calling readv(2) with iov_len &lt; 0 or &gt; INT_MAX would result in a  Calling readv(2) with iov_len &lt; 0 or &gt; INT_MAX would result in a
Line 122 
Line 122 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.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="inetd"></a>  <li id="inetd">
 <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>
 Inetd had a file descriptor leak.  A patch is  Inetd had a file descriptor leak.  A patch is
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <li><a name="unionfs"></a>  <li id="unionfs">
 <font color="#009000"><strong>BUG FIX</strong></font>  <font color="#009000"><strong>BUG FIX</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 As shipped, unionfs had some serious problems.  As shipped, unionfs had some serious problems.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch">
 A patch is available to solve this</a>.  A patch is available to solve this</a>.
 <p>  <p>
 <li><a name="fdalloc"></a>  <li id="fdalloc">
 <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>
 Some non-allocated file descriptors have implied uses according to  Some non-allocated file descriptors have implied uses according to
Line 147 
Line 147 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <li><a name="resolver"></a>  <li id="resolver">
 <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 benign looking buffer overflow in the resolver routines was re-introduced  A benign looking buffer overflow in the resolver routines was re-introduced
Line 156 
Line 156 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <li><a name="xlib"></a>  <li id="xlib">
 <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>
 Vulnerabilities have been found in the X11, Xt, Xaw and Xmu  Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
Line 172 
Line 172 
 The 2nd source patch</a> for these problems, specifically adapted to the  The 2nd source patch</a> for these problems, specifically adapted to the
 OpenBSD 2.3 X11 tree, is available now.  OpenBSD 2.3 X11 tree, is available now.
 <p>  <p>
 <li><a name="kill"></a>  <li id="kill">
 <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>
 The kill(2) system call previously would permit a large set of signals to  The kill(2) system call previously would permit a large set of signals to
Line 183 
Line 183 
 The fourth revision of a source code patch which solves the problem is  The fourth revision of a source code patch which solves the problem is
 available.</a>  available.</a>
 <p>  <p>
 <li><a name="immutable"></a>  <li id="immutable">
 <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 possible new security problem exists if you rely on securelevels and  A possible new security problem exists if you rely on securelevels and
Line 194 
Line 194 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.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="ipsec"></a>  <li id="ipsec">
 <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>
 If IPSEC communication is attempted by starting photurisd(8) (which is  If IPSEC communication is attempted by starting photurisd(8) (which is
Line 203 
Line 203 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <a name="xterm-xaw"></a>  <li id="xterm-xaw">
 <li><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>
 As stated in CERT advisory VB-98.04, there are buffer  As stated in CERT advisory VB-98.04, there are buffer
 overrun problems in <strong>xterm</strong> related to the input-Method,  overrun problems in <strong>xterm</strong> related to the input-Method,
Line 234 
Line 234 
 and  and
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.
 <p>  <p>
 <li><a name="pctr"></a>  <li id="pctr">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>  <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 The pctr(4) driver has bugs that permit any user to crash the machine,  The pctr(4) driver has bugs that permit any user to crash the machine,
 if the CPU is not an Intel CPU.  This problem has been properly fixed  if the CPU is not an Intel CPU.  This problem has been properly fixed
Line 254 
Line 254 
 <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c  <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
 </ul>  </ul>
 <p>  <p>
 <a name="pcvt"></a>  <li id="pcvt">
 <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>  <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 The pcvt(4) console driver has a bug that can cause some keyboard  The pcvt(4) console driver has a bug that can cause some keyboard
 controllers to lock up when a key is pressed that toggles the status  controllers to lock up when a key is pressed that toggles the status
 of a keyboard LED (scroll lock, caps lock, etc).  The problem is  of a keyboard LED (scroll lock, caps lock, etc).  The problem is
Legend:
Removed from v.1.66  
changed lines
  Added in v.1.67