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

Diff for /www/errata47.html between version 1.30 and 1.31

version 1.30, 2014/03/31 03:12:47 version 1.31, 2014/03/31 16:02:48
Line 77 
Line 77 
   
 <ul>  <ul>
 <li><a name="013_pf"></a>  <li><a name="013_pf"></a>
 <font color="#009000"><strong>013: SECURITY FIX: February 16, 2011</strong></font> &nbsp; <i>Little-endian architectures</i><br>  <font color="#009000"><strong>013: SECURITY FIX: February 16, 2011</strong></font>
   &nbsp; <i>Little-endian architectures</i><br>
 PF rules specifying address ranges (e.g. "10.1.1.1 - 10.1.1.5") were  PF rules specifying address ranges (e.g. "10.1.1.1 - 10.1.1.5") were
 not correctly handled on little-endian systems (alpha, amd64, arm, i386,  not correctly handled on little-endian systems (alpha, amd64, arm, i386,
 mips64el, vax). Other address types (bare addresses "10.1.1.1" and  mips64el, vax). Other address types (bare addresses "10.1.1.1" and
Line 88 
Line 89 
 <p>  <p>
   
 <li><a name="012_openssl"></a>  <li><a name="012_openssl"></a>
 <font color="#009000"><strong>012: SECURITY FIX: February 11, 2011</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>012: SECURITY FIX: February 11, 2011</strong></font>
   &nbsp; <i>All architectures</i><br>
 An incorrectly formatted ClientHello handshake message could cause  An incorrectly formatted ClientHello handshake message could cause
 OpenSSL to parse past the end of the message.  An attacker could use this flaw  OpenSSL to parse past the end of the message.  An attacker could use this flaw
 to trigger an invalid memory access, causing a crash of an application linked  to trigger an invalid memory access, causing a crash of an application linked
Line 105 
Line 107 
 <p>  <p>
   
 <li><a name="011_rtsock"></a>  <li><a name="011_rtsock"></a>
 <font color="#009000"><strong>011: RELIABILITY FIX: January 13, 2011</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>011: RELIABILITY FIX: January 13, 2011</strong></font>
   &nbsp; <i>All architectures</i><br>
 sp_protocol in RTM_DELETE messages could contain garbage values  sp_protocol in RTM_DELETE messages could contain garbage values
 leading to routing socket users that restrict the AF (such as ospfd)  leading to routing socket users that restrict the AF (such as ospfd)
 not seeing any of the RTM_DELETE messages.  not seeing any of the RTM_DELETE messages.
Line 115 
Line 118 
 <p>  <p>
   
 <li><a name="010_cbc"></a>  <li><a name="010_cbc"></a>
 <font color="#009000"><strong>010: RELIABILITY FIX: December 20, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>010: RELIABILITY FIX: December 20, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Bring CBC oracle attack countermeasures to hardware crypto accelerator land.  Bring CBC oracle attack countermeasures to hardware crypto accelerator land.
 This fixes aes-ni, via xcrypt and various drivers  This fixes aes-ni, via xcrypt and various drivers
 (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=glxsb&arch=i386&sektion=4">glxsb(4)</a>,  (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=glxsb&arch=i386&sektion=4">glxsb(4)</a>,
Line 131 
Line 135 
   
   
 <li><a name="009_pf"></a>  <li><a name="009_pf"></a>
 <font color="#009000"><strong>009: SECURITY FIX: December 17, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>009: SECURITY FIX: December 17, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Insufficent initialization of the pf rule structure in the ioctl  Insufficent initialization of the pf rule structure in the ioctl
 handler may allow userland to modify kernel memory. By default root  handler may allow userland to modify kernel memory. By default root
 privileges are needed to add or modify pf rules.  privileges are needed to add or modify pf rules.
Line 141 
Line 146 
 <p>  <p>
   
 <li><a name="008_openssl"></a>  <li><a name="008_openssl"></a>
 <font color="#009000"><strong>008: RELIABILITY FIX: November 17, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>008: RELIABILITY FIX: November 17, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Fix a flaw in the OpenSSL TLS server extension code parsing which could lead to  Fix a flaw in the OpenSSL TLS server extension code parsing which could lead to
 a buffer overflow. This affects OpenSSL based TLS servers which are multi-threaded  a buffer overflow. This affects OpenSSL based TLS servers which are multi-threaded
 and use OpenSSL's internal caching mechanism. Servers that are multi-process  and use OpenSSL's internal caching mechanism. Servers that are multi-process
Line 152 
Line 158 
 <p>  <p>
   
 <li><a name="007_scsi"></a>  <li><a name="007_scsi"></a>
 <font color="#009000"><strong>007: RELIABILITY FIX: September 14, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>007: RELIABILITY FIX: September 14, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Avoid calling scsi_done() more than once in gdt(4). Fixes a kernel panic triggered by syncing disks during shut down.<br>  Avoid calling scsi_done() more than once in gdt(4). Fixes a kernel panic triggered by syncing disks during shut down.<br>
 Clear the ITSDONE flag before issuing commands to the SCSI adapter. Fixes handling of retried SCSI commands.  Clear the ITSDONE flag before issuing commands to the SCSI adapter. Fixes handling of retried SCSI commands.
 <br>  <br>
Line 161 
Line 168 
 <p>  <p>
   
 <li><a name="006_scsi"></a>  <li><a name="006_scsi"></a>
 <font color="#009000"><strong>006: RELIABILITY FIX: July 8, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>006: RELIABILITY FIX: July 8, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 Restore an unusual XS_SENSE semantic. Fixes dump(8)/restore(8) problems seen on certain tape drives.  Restore an unusual XS_SENSE semantic. Fixes dump(8)/restore(8) problems seen on certain tape drives.
 <br>  <br>
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/006_scsi.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/006_scsi.patch">
Line 169 
Line 177 
 <p>  <p>
   
 <li><a name="005_pfsync"></a>  <li><a name="005_pfsync"></a>
 <font color="#009000"><strong>005: RELIABILITY FIX: May 14, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>005: 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.7/common/005_pfsync.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/005_pfsync.patch">
Line 177 
Line 186 
 <p>  <p>
   
 <li><a name="004_pfsync"></a>  <li><a name="004_pfsync"></a>
 <font color="#009000"><strong>004: SECURITY FIX: April 23, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>004: SECURITY FIX: April 23, 2010</strong></font>
   &nbsp; <i>All architectures</i><br>
 The combination of pfsync and IPSEC may crash the kernel.<br>  The combination of pfsync and IPSEC may crash the kernel.<br>
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/004_pfsync.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/004_pfsync.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="003_openssl"></a>  <li><a name="003_openssl"></a>
 <font color="#009000"><strong>003: SECURITY FIX: April 14, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>003: 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 193 
Line 204 
 <p>  <p>
   
 <li><a name="002_mpi"></a>  <li><a name="002_mpi"></a>
 <font color="#009000"><strong>002: RELIABILITY FIX: April 4, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>002: 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 207 
Line 219 
 <p>  <p>
   
 <li><a name="001_kerberos"></a>  <li><a name="001_kerberos"></a>
 <font color="#009000"><strong>001: RELIABILITY FIX: March 31, 2010</strong></font> &nbsp; <i>All architectures</i><br>  <font color="#009000"><strong>001: 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.

Legend:
Removed from v.1.30  
changed lines
  Added in v.1.31