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

Diff for /www/errata43.html between version 1.40 and 1.41

version 1.40, 2014/03/31 03:12:47 version 1.41, 2014/03/31 16:02:48
Line 78 
Line 78 
 <ul>  <ul>
   
 <li><a name="013_pf"></a>  <li><a name="013_pf"></a>
 <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font>
   &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,
 a null pointer dereference will occur, resulting in a kernel panic.  a null pointer dereference will occur, resulting in a kernel panic.
 In certain configurations this may be triggered by a remote attacker.  In certain configurations this may be triggered by a remote attacker.
Line 98 
Line 99 
 <p>  <p>
   
 <li><a name="012_openssl"></a>  <li><a name="012_openssl"></a>
 <font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font>
   &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
 accesses through the use of certain invalid strings  accesses through the use of certain invalid strings
 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>)  (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>)
Line 115 
Line 117 
 <p>  <p>
   
 <li><a name="011_sudo"></a>  <li><a name="011_sudo"></a>
 <font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font>
   &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
 as a different user than their access rule specifies when a Unix  as a different user than their access rule specifies when a Unix
 group is used in the RunAs portion of the rule.  The bug only manifests  group is used in the RunAs portion of the rule.  The bug only manifests
Line 127 
Line 130 
 <p>  <p>
   
 <li><a name="010_bgpd"></a>  <li><a name="010_bgpd"></a>
 <font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font>
   &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
 the process to terminate because of the resulting corrupt path.  the process to terminate because of the resulting corrupt path.
 <br>  <br>
Line 136 
Line 140 
 <p>  <p>
   
 <li><a name="009_bgpd"></a>  <li><a name="009_bgpd"></a>
 <font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font>
   &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 -
 adhering to the RFCs - closed the session to the neighbor.  adhering to the RFCs - closed the session to the neighbor.
 This error in the specification allowed 3rd parties to close remote BGP  This error in the specification allowed 3rd parties to close remote BGP
Line 148 
Line 153 
 <p>  <p>
   
 <li><a name="008_bind"></a>  <li><a name="008_bind"></a>
 <font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font>
   &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
 function, potentially allowing bypass of verification of DNSSEC DSA  function, potentially allowing bypass of verification of DNSSEC DSA
 signatures.  signatures.
Line 159 
Line 165 
 <p>  <p>
   
 <li><a name="007_openssl"></a>  <li><a name="007_openssl"></a>
 <font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font>
   &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
 certain verification functions, allowing validation to be bypassed and  certain verification functions, allowing validation to be bypassed and
 permitting a remote attacker to conduct a "man in the middle attack"  permitting a remote attacker to conduct a "man in the middle attack"
Line 172 
Line 179 
 <p>  <p>
   
 <li><a name="006_ndp"></a>  <li><a name="006_ndp"></a>
 <font color="#009000"><strong>006: SECURITY FIX: October 2, 2008</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>006: SECURITY FIX: October 2, 2008</strong></font>
   &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
 solicitation requests maybe allowing a nearby attacker to intercept traffic.  solicitation requests maybe allowing a nearby attacker to intercept traffic.
 The attacker must have IPv6 connectivity to the same router as their target for  The attacker must have IPv6 connectivity to the same router as their target for
Line 184 
Line 192 
 <p>  <p>
   
 <li><a name="005_pcb"></a>  <li><a name="005_pcb"></a>
 <font color="#009000"><strong>005: RELIABILITY FIX: July 29, 2008</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>005: RELIABILITY FIX: July 29, 2008</strong></font>
   &nbsp; <i>All architectures</i><br>
 Some kinds of IPv6 usage would leak kernel memory (in particular, this path  Some kinds of IPv6 usage would leak kernel memory (in particular, this path
 was exercised by the named(8) patch for port randomization).  Since INET6 is  was exercised by the named(8) patch for port randomization).  Since INET6 is
 enabled by default, this condition affects all systems.  enabled by default, this condition affects all systems.
Line 194 
Line 203 
 <p>  <p>
   
 <li><a name="004_bind"></a>  <li><a name="004_bind"></a>
 <font color="#009000"><strong>004: SECURITY FIX: July 23, 2008</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>004: SECURITY FIX: July 23, 2008</strong></font>
   &nbsp; <i>All architectures</i><br>
 <strong>2nd revision, July 23, 2008</strong><br>  <strong>2nd revision, July 23, 2008</strong><br>
 A vulnerability has been found with BIND. An attacker could use this vulnerability  A vulnerability has been found with BIND. An attacker could use this vulnerability
 to poison the cache of a recursive resolving name server.  to poison the cache of a recursive resolving name server.
Line 205 
Line 215 
 <p>  <p>
   
 <li><a name="003_xorg"></a>  <li><a name="003_xorg"></a>
 <font color="#009000"><strong>003: SECURITY FIX: July 15, 2008</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>003: SECURITY FIX: July 15, 2008</strong></font>
   &nbsp; <i>All architectures</i><br>
 Multiple vulnerabilities have been discovered in X.Org.<br>  Multiple vulnerabilities have been discovered in X.Org.<br>
 RENDER Extension heap buffer overflow,  RENDER Extension heap buffer overflow,
 RENDER Extension crash,  RENDER Extension crash,
Line 223 
Line 234 
 <p>  <p>
   
 <li><a name="002_openssh2"></a>  <li><a name="002_openssh2"></a>
 <font color="#009000"><strong>002: SECURITY FIX: April 3, 2008</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>002: SECURITY FIX: April 3, 2008</strong></font>
   &nbsp; <i>All architectures</i><br>
 Avoid possible hijacking of X11-forwarded connections with sshd(8)  Avoid possible hijacking of X11-forwarded connections with sshd(8)
 by refusing to listen on a port unless all address families bind  by refusing to listen on a port unless all address families bind
 successfully.<br>  successfully.<br>
Line 232 
Line 244 
 <p>  <p>
   
 <li><a name="001_openssh"></a>  <li><a name="001_openssh"></a>
 <font color="#009000"><strong>001: SECURITY FIX: March 30, 2008</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>001: SECURITY FIX: March 30, 2008</strong></font>
   &nbsp; <i>All architectures</i><br>
 sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) <em>ForceCommand</em>  sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) <em>ForceCommand</em>
 directive was in effect, allowing users with write access to this file to  directive was in effect, allowing users with write access to this file to
 execute arbitrary commands. This behaviour was documented, but was an unsafe  execute arbitrary commands. This behaviour was documented, but was an unsafe

Legend:
Removed from v.1.40  
changed lines
  Added in v.1.41