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

Diff for /www/errata44.html between version 1.42 and 1.43

version 1.42, 2014/10/02 14:34:45 version 1.43, 2015/02/14 04:36:51
Line 81 
Line 81 
 <hr>  <hr>
   
 <ul>  <ul>
 <li><a name="016_getsockopt"></a>  <li id="016_getsockopt">
 <font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font>  <font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &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,
Line 91 
Line 91 
 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="015_xmm"></a>  <li id="015_xmm">
 <font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font>  <font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font>
 &nbsp; <i>i386 only</i><br>  &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.
Line 100 
Line 100 
 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="014_bind"></a>  <li id="014_bind">
 <font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font>  <font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &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
Line 112 
Line 112 
 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="013_pf"></a>  <li id="013_pf">
 <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font>  <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 When pf attempts to perform translation on a specially crafted IP datagram,  When pf attempts to perform translation on a specially crafted IP datagram,
Line 133 
Line 133 
 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="012_openssl"></a>  <li id="012_openssl">
 <font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font>  <font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The OpenSSL ASN.1 handling code could be forced to perform invalid memory  The OpenSSL ASN.1 handling code could be forced to perform invalid memory
Line 151 
Line 151 
 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="011_sudo"></a>  <li id="011_sudo">
 <font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font>  <font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 sudo(8) may allow a user listed in the sudoers file to run a command  sudo(8) may allow a user listed in the sudoers file to run a command
Line 164 
Line 164 
 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="010_bgpd"></a>  <li id="010_bgpd">
 <font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font>  <font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 bgpd(8) did not correctly prepend its own AS to very long AS paths, causing  bgpd(8) did not correctly prepend its own AS to very long AS paths, causing
Line 174 
Line 174 
 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="009_bgpd"></a>  <li id="009_bgpd">
 <font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font>  <font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Upon reception of an invalid update with 4-byte AS attributes, bgpd -  Upon reception of an invalid update with 4-byte AS attributes, bgpd -
Line 187 
Line 187 
 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="008_bind"></a>  <li id="008_bind">
 <font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font>  <font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 named(8) did not correctly check the return value of a DSA verification  named(8) did not correctly check the return value of a DSA verification
Line 199 
Line 199 
 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="007_openssl"></a>  <li id="007_openssl">
 <font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font>  <font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The OpenSSL libraries did not correctly check the return value from  The OpenSSL libraries did not correctly check the return value from
Line 213 
Line 213 
 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="006_dhcpd"></a>  <li id="006_dhcpd">
 <font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font>  <font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Due to changes in the options handling this caused problems with some  Due to changes in the options handling this caused problems with some
Line 224 
Line 224 
 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="005_pglistalloc"></a>  <li id="005_pglistalloc">
 <font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font>  <font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A software bug could cause memory allocation to cause a kernel panic  A software bug could cause memory allocation to cause a kernel panic
Line 234 
Line 234 
 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="004_httpd"></a>  <li id="004_httpd">
 <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font>  <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Fix  Fix
Line 247 
Line 247 
 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="003_tcpinput"></a>  <li id="003_tcpinput">
 <font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font>  <font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Fix the IPv4 TCP/IP stack's TIME_WAIT socket recycling. Due to the bug this  Fix the IPv4 TCP/IP stack's TIME_WAIT socket recycling. Due to the bug this
Line 258 
Line 258 
 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="002_vr"></a>  <li id="002_vr">
 <font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font>  <font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Due to a bug in the vr(4) driver it is possible for a system using the vr(4)  Due to a bug in the vr(4) driver it is possible for a system using the vr(4)
Line 268 
Line 268 
 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="001_ndp"></a>  <li id="001_ndp">
 <font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font>  <font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor  The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor
Legend:
Removed from v.1.42  
changed lines
  Added in v.1.43