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

Diff for /www/errata22.html between version 1.70 and 1.71

version 1.70, 2014/03/31 03:12:47 version 1.71, 2014/03/31 03:36:54
Line 74 
Line 74 
   
 <hr>  <hr>
   
 <a name="all"></a>  
 <h3><font color="#e00000">All architectures</font></h3>  
 <ul>  <ul>
 <li><a name="ipsec"></a>  <li><a name="ipsec"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &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
 disabled by default), a system crash may be evoked from remote if  disabled by default), a system crash may be evoked from remote if
 an attacker uses some classes of invalid packets.  an attacker uses some classes of invalid packets.
Line 86 
Line 84 
 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="xterm-xaw"></a>  <li><a name="xterm-xaw"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &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,
 preeditType, and *Keymap resources. Additional buffer overruns exist in  preeditType, and *Keymap resources. Additional buffer overruns exist in
Line 101 
Line 99 
 We provide a version of this patch file specifically for the OpenBSD 2.2 tree</a>.  We provide a version of this patch file specifically for the OpenBSD 2.2 tree</a>.
 <p>  <p>
 <li><a name="rmjob"></a>  <li><a name="rmjob"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 An exploitable buffer mismanagement exists in a subroutine used by  An exploitable buffer mismanagement exists in a subroutine used by
 lprm and lpd.  The problem is exploitable by users on a particular  lprm and lpd.  The problem is exploitable by users on a particular
 machine if there is an entry in <strong>/etc/printcap</strong> which  machine if there is an entry in <strong>/etc/printcap</strong> which
Line 110 
Line 108 
 A patch is available which corrects this behaviour</a>.  A patch is available which corrects this behaviour</a>.
 <p>  <p>
 <li><a name="uucpd"></a>  <li><a name="uucpd"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A DNS-based vulnerability exists when uucpd is used.  By default uucpd  A DNS-based vulnerability exists when uucpd is used.  By default uucpd
 is not enabled in the OpenBSD releases, but some sites may have enabled it.  is not enabled in the OpenBSD releases, but some sites may have enabled it.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch">
 A patch is available which corrects this behaviour</a>.  A patch is available which corrects this behaviour</a>.
 <p>  <p>
 <li><a name="named"></a>  <li><a name="named"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A vulnerability exists when (and only when) /etc/named.conf has the  A vulnerability exists when (and only when) /etc/named.conf has the
 <strong>fake-iquery</strong> option enabled.  <strong>fake-iquery</strong> option enabled.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch">
 A patch is available which corrects this behaviour</a>.  A patch is available which corrects this behaviour</a>.
 <p>  <p>
 <li><a name="ping"></a>  <li><a name="ping"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A vulnerability exists in ping(8); if the -R option is used to record  A vulnerability exists in ping(8); if the -R option is used to record
 routes, an attacker can spoof a reply packet that will overflow inside  routes, an attacker can spoof a reply packet that will overflow inside
 ping.  Preliminary investigation makes it look the worst attack  ping.  Preliminary investigation makes it look the worst attack
Line 133 
Line 131 
 A patch is available which corrects this behaviour</a>.  A patch is available which corrects this behaviour</a>.
 <p>  <p>
 <li><a name="sourceroute"></a>  <li><a name="sourceroute"></a>
 <strong><font color="#009000">SECURITY FIX</font></strong><br>  <strong><font color="#009000">SECURITY FIX</font></strong> &nbsp; <i>All architectures</i><br>
 If the sysctl variable <strong>net.inet.ip.forwarding</strong> is  If the sysctl variable <strong>net.inet.ip.forwarding</strong> is
 enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>  enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>
 is disabled (value 0), the kernel will block source routed packets from  is disabled (value 0), the kernel will block source routed packets from
Line 145 
Line 143 
 A kernel patch is provided</a>.  A kernel patch is provided</a>.
 <p>  <p>
 <li><a name="ruserok"></a>  <li><a name="ruserok"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A combination localhost+remote host security problem exists if a  A combination localhost+remote host security problem exists if a
 local user running a setuid binary causes a non-existent root .rhosts  local user running a setuid binary causes a non-existent root .rhosts
 file to be created via a symbolic link with a specific kind of corefile,  file to be created via a symbolic link with a specific kind of corefile,
Line 177 
Line 175 
 ssh 1.2.21 and previous (the ssh people have been alerted).  ssh 1.2.21 and previous (the ssh people have been alerted).
 <p>  <p>
 <li><a name="mmap"></a>  <li><a name="mmap"></a>
 <strong><font color="#009000">SECURITY FIX</font></strong><br>  <strong><font color="#009000">SECURITY FIX</font></strong> &nbsp; <i>All architectures</i><br>
 A bug in the vm system permits a file descriptor opened read-only on a  A bug in the vm system permits a file descriptor opened read-only on a
 device, to later on be mmap(2)'d read-write, and then modified.  This  device, to later on be mmap(2)'d read-write, and then modified.  This
 does not result in a security hole by itself, but it does violate the  does not result in a security hole by itself, but it does violate the
Line 188 
Line 186 
 A kernel patch is available which corrects this behaviour (this is  A kernel patch is available which corrects this behaviour (this is
 revision 3 of this patch)</a>.  revision 3 of this patch)</a>.
 <p>  <p>
 <li><font color="#009000"><strong>BUILD PROCESS FIX</strong></font><br>  <li><font color="#009000"><strong>BUILD PROCESS FIX</strong></font> &nbsp; <i>All architectures</i><br>
 Building an object tree from a read-only source tree (such as off a CDROM)  Building an object tree from a read-only source tree (such as off a CDROM)
 may fail under certain circumstances (e.g. when creating a symlink on sparc  may fail under certain circumstances (e.g. when creating a symlink on sparc
 whose target name is exactly 33 characters).  As a workaround you have to  whose target name is exactly 33 characters).  As a workaround you have to
Line 198 
Line 196 
 A replacement source file exists</a>.  A replacement source file exists</a>.
 <p>  <p>
 <li><a name="mountd"></a>  <li><a name="mountd"></a>
 <font color="#009000"><strong>SECURITY FIX</strong></font><br>  <font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 If a line in /etc/exports which contains hostnames results in an empty  If a line in /etc/exports which contains hostnames results in an empty
 list because none of the supplied hostnames is known, mountd(8) will  list because none of the supplied hostnames is known, mountd(8) will
 accidentally export the filesystem to the world.  accidentally export the filesystem to the world.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch">
 A patch is available which corrects this behaviour</a>.  A patch is available which corrects this behaviour</a>.
 <p>  <p>
 <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>  <li><font color="#009000"><strong>RELIABILITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 Setting the MSG_EOR flag on a tcp packet in the send(2) family of  Setting the MSG_EOR flag on a tcp packet in the send(2) family of
 system calls could cause a kernel panic.  system calls could cause a kernel panic.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch">

Legend:
Removed from v.1.70  
changed lines
  Added in v.1.71