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

Diff for /www/errata46.html between version 1.28 and 1.29

version 1.28, 2014/03/31 03:12:47 version 1.29, 2014/03/31 16:02:48
Line 77 
Line 77 
   
 <ul>  <ul>
 <li><a name="012_trunklacp"></a>  <li><a name="012_trunklacp"></a>
 <font color="#009000"><strong>012: RELIABILITY FIX: May 14, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>012: RELIABILITY FIX: May 14, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Insufficient protection of the trunk interface queues may cause  Insufficient protection of the trunk interface queues may cause
 LACP trunks to fail under load.  LACP trunks to fail under load.
 <br>  <br>
Line 86 
Line 87 
 <p>  <p>
   
 <li><a name="011_pfsync"></a>  <li><a name="011_pfsync"></a>
 <font color="#009000"><strong>011: RELIABILITY FIX: May 14, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>011: RELIABILITY FIX: May 14, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Incorrectly initialized state updates can cause pfsync update storms.  Incorrectly initialized state updates can cause pfsync update storms.
 <br>  <br>
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/011_pfsync.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/011_pfsync.patch">
Line 94 
Line 96 
 <p>  <p>
   
 <li><a name="010_openssl"></a>  <li><a name="010_openssl"></a>
 <font color="#009000"><strong>010: SECURITY FIX: April 14, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>010: SECURITY FIX: April 14, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 In TLS connections, certain incorrectly formatted records can cause  In TLS connections, certain incorrectly formatted records can cause
 an OpenSSL client or server to crash due to a read attempt at NULL.  an OpenSSL client or server to crash due to a read attempt at NULL.
 <br>  <br>
Line 103 
Line 106 
 <p>  <p>
   
 <li><a name="009_mpi"></a>  <li><a name="009_mpi"></a>
 <font color="#009000"><strong>009: RELIABILITY FIX: April 4, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>009: RELIABILITY FIX: April 4, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 When updating sensors showing the state of RAID volumes  When updating sensors showing the state of RAID volumes
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mpi&sektion=4">mpi(4)</a>  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mpi&sektion=4">mpi(4)</a>
 allocates temporary memory and then returns it to the kernel as  allocates temporary memory and then returns it to the kernel as
Line 117 
Line 121 
 <p>  <p>
   
 <li><a name="008_kerberos"></a>  <li><a name="008_kerberos"></a>
 <font color="#009000"><strong>008: RELIABILITY FIX: March 31, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>008: RELIABILITY FIX: March 31, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 When decrypting packets, the internal decryption functions were not  When decrypting packets, the internal decryption functions were not
 paranoid enough in checking for underruns, which could potentially  paranoid enough in checking for underruns, which could potentially
 lead to crashes.  lead to crashes.
Line 127 
Line 132 
 <p>  <p>
   
 <li><a name="007_ftpd"></a>  <li><a name="007_ftpd"></a>
 <font color="#009000"><strong>007: RELIABILITY FIX: March 12, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>007: RELIABILITY FIX: March 12, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Due to a null pointer dereference, it would be possible to crash ftpd when  Due to a null pointer dereference, it would be possible to crash ftpd when
 handling glob(3)'ing requests. This is non-exploitable.  handling glob(3)'ing requests. This is non-exploitable.
 <br>  <br>
Line 136 
Line 142 
 <p>  <p>
   
 <li><a name="006_openssl"></a>  <li><a name="006_openssl"></a>
 <font color="#009000"><strong>006: SECURITY FIX: March 12, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>006: SECURITY FIX: March 12, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 OpenSSL is susceptible to a buffer overflow due to a failure  OpenSSL is susceptible to a buffer overflow due to a failure
 to check for NULL returns from bn_wexpand function calls.  to check for NULL returns from bn_wexpand function calls.
 <br>  <br>
Line 145 
Line 152 
 <p>  <p>
   
 <li><a name="005_ptrace"></a>  <li><a name="005_ptrace"></a>
 <font color="#009000"><strong>005: RELIABILITY FIX: January 29, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>005: RELIABILITY FIX: January 29, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 By using ptrace(2) on an ancestor process, a loop in the process tree  By using ptrace(2) on an ancestor process, a loop in the process tree
 could be created, violating assumptions in other parts of the kernel  could be created, violating assumptions in other parts of the kernel
 and resulting in infinite loops.  and resulting in infinite loops.
Line 155 
Line 163 
 <p>  <p>
   
 <li><a name="004_openssl"></a>  <li><a name="004_openssl"></a>
 <font color="#009000"><strong>004: SECURITY FIX: November 26, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>004: SECURITY FIX: November 26, 2009</strong></font>
   &nbsp; <i>All architectures</i><br>
 The SSL/TLS protocol is subject to man-in-the-middle attacks related to  The SSL/TLS protocol is subject to man-in-the-middle attacks related to
 renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).  renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).
 OpenSSL permitted this protocol feature by default and had no way to  OpenSSL permitted this protocol feature by default and had no way to
Line 166 
Line 175 
 <p>  <p>
   
 <li><a name="003_getsockopt"></a>  <li><a name="003_getsockopt"></a>
 <font color="#009000"><strong>003: RELIABILITY FIX: October 28, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>003: RELIABILITY FIX: October 28, 2009</strong></font>
   &nbsp; <i>All architectures</i><br>
 getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,  getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
 IP_IPCOMP_LEVEL will crash the system.  IP_IPCOMP_LEVEL will crash the system.
 <br>  <br>
Line 175 
Line 185 
 <p>  <p>
   
 <li><a name="002_xmm"></a>  <li><a name="002_xmm"></a>
 <font color="#009000"><strong>002: RELIABILITY FIX: October 05, 2009</strong></font> &nbsp; <i>i386 only</i><br>  <font color="#009000"><strong>002: RELIABILITY FIX: October 05, 2009</strong></font>
   &nbsp; <i>i386 only</i><br>
 XMM exceptions are not correctly handled resulting in a kernel panic.  XMM exceptions are not correctly handled resulting in a kernel panic.
 <br>  <br>
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.6/i386/002_xmm.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.6/i386/002_xmm.patch">
Line 183 
Line 194 
 <p>  <p>
   
 <li><a name="001_bind"></a>  <li><a name="001_bind"></a>
 <font color="#009000"><strong>001: RELIABILITY FIX: July 29, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>001: RELIABILITY FIX: July 29, 2009</strong></font>
   &nbsp; <i>All architectures</i><br>
 A vulnerability has been found in BIND's named server  A vulnerability has been found in BIND's named server
 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).  (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).
 An attacker could crash a server with a specially crafted dynamic update message to a  An attacker could crash a server with a specially crafted dynamic update message to a
Legend:
Removed from v.1.28  
changed lines
  Added in v.1.29