===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata46.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -c -r1.54 -r1.55
*** www/errata46.html	2019/05/27 22:55:20	1.54
--- www/errata46.html	2019/05/28 16:32:42	1.55
***************
*** 84,141 ****
  <hr>
  
  <ul>
! <li id="p012_trunklacp">
! <strong>012: RELIABILITY FIX: May 14, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! Insufficient protection of the trunk interface queues may cause
! LACP trunks to fail under load.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/012_trunklacp.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p011_pfsync">
! <strong>011: RELIABILITY FIX: May 14, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! Incorrectly initialized state updates can cause pfsync update storms.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/011_pfsync.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p010_openssl">
! <strong>010: SECURITY FIX: April 14, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! In TLS connections, certain incorrectly formatted records can cause
! an OpenSSL client or server to crash due to a read attempt at NULL.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/010_openssl.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p009_mpi">
! <strong>009: RELIABILITY FIX: April 4, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! When updating sensors showing the state of RAID volumes
! <a href="https://man.openbsd.org/OpenBSD-4.6/mpi.4">mpi(4)</a>
! allocates temporary memory and then returns it to the kernel as
! device memory.
! This causes kernel memory usage to be misrepresented, eventually
! leading to a denial of service when a resource limit is apparently
! reached.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/009_mpi.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p008_kerberos">
! <strong>008: RELIABILITY FIX: March 31, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! When decrypting packets, the internal decryption functions were not
! paranoid enough in checking for underruns, which could potentially
! lead to crashes.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/008_kerberos.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
--- 84,151 ----
  <hr>
  
  <ul>
! 
! <li id="p001_bind">
! <strong>001: RELIABILITY FIX: July 29, 2009</strong>
  &nbsp; <i>All architectures</i><br>
! 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>).
! An attacker could crash a server with a specially crafted dynamic update message to a
! zone for which the server is master.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/001_bind.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p002_xmm">
! <strong>002: RELIABILITY FIX: October 05, 2009</strong>
! &nbsp; <i>i386 only</i><br>
! XMM exceptions are not correctly handled resulting in a kernel panic.
! <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/i386/002_xmm.patch">
! A source code patch exists which remedies this problem.</a>
! <p>
! 
! <li id="p003_getsockopt">
! <strong>003: RELIABILITY FIX: October 28, 2009</strong>
  &nbsp; <i>All architectures</i><br>
! getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
! IP_IPCOMP_LEVEL will crash the system.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/003_getsockopt.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p004_openssl">
! <strong>004: SECURITY FIX: November 26, 2009</strong>
  &nbsp; <i>All architectures</i><br>
! The SSL/TLS protocol is subject to man-in-the-middle attacks related to
! renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).
! OpenSSL permitted this protocol feature by default and had no way to
! disable it.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/004_openssl.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p005_ptrace">
! <strong>005: RELIABILITY FIX: January 29, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! 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
! and resulting in infinite loops.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/005_ptrace.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p006_openssl">
! <strong>006: SECURITY FIX: March 12, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! OpenSSL is susceptible to a buffer overflow due to a failure
! to check for NULL returns from bn_wexpand function calls.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/006_openssl.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
***************
*** 149,215 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p006_openssl">
! <strong>006: SECURITY FIX: March 12, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! OpenSSL is susceptible to a buffer overflow due to a failure
! to check for NULL returns from bn_wexpand function calls.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/006_openssl.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p005_ptrace">
! <strong>005: RELIABILITY FIX: January 29, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! 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
! and resulting in infinite loops.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/005_ptrace.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p004_openssl">
! <strong>004: SECURITY FIX: November 26, 2009</strong>
  &nbsp; <i>All architectures</i><br>
! The SSL/TLS protocol is subject to man-in-the-middle attacks related to
! renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).
! OpenSSL permitted this protocol feature by default and had no way to
! disable it.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/004_openssl.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p003_getsockopt">
! <strong>003: RELIABILITY FIX: October 28, 2009</strong>
  &nbsp; <i>All architectures</i><br>
! getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
! IP_IPCOMP_LEVEL will crash the system.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/003_getsockopt.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p002_xmm">
! <strong>002: RELIABILITY FIX: October 05, 2009</strong>
! &nbsp; <i>i386 only</i><br>
! XMM exceptions are not correctly handled resulting in a kernel panic.
! <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/i386/002_xmm.patch">
! A source code patch exists which remedies this problem.</a>
! <p>
! 
! <li id="p001_bind">
! <strong>001: RELIABILITY FIX: July 29, 2009</strong>
  &nbsp; <i>All architectures</i><br>
! 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>).
! An attacker could crash a server with a specially crafted dynamic update message to a
! zone for which the server is master.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/001_bind.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
--- 159,216 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p008_kerberos">
! <strong>008: RELIABILITY FIX: March 31, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! When decrypting packets, the internal decryption functions were not
! paranoid enough in checking for underruns, which could potentially
! lead to crashes.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/008_kerberos.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p009_mpi">
! <strong>009: RELIABILITY FIX: April 4, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! When updating sensors showing the state of RAID volumes
! <a href="https://man.openbsd.org/OpenBSD-4.6/mpi.4">mpi(4)</a>
! allocates temporary memory and then returns it to the kernel as
! device memory.
! This causes kernel memory usage to be misrepresented, eventually
! leading to a denial of service when a resource limit is apparently
! reached.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/009_mpi.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p010_openssl">
! <strong>010: SECURITY FIX: April 14, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! In TLS connections, certain incorrectly formatted records can cause
! an OpenSSL client or server to crash due to a read attempt at NULL.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/010_openssl.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p011_pfsync">
! <strong>011: RELIABILITY FIX: May 14, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! Incorrectly initialized state updates can cause pfsync update storms.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/011_pfsync.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p012_trunklacp">
! <strong>012: RELIABILITY FIX: May 14, 2010</strong>
  &nbsp; <i>All architectures</i><br>
! Insufficient protection of the trunk interface queues may cause
! LACP trunks to fail under load.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.6/common/012_trunklacp.patch">
  A source code patch exists which remedies this problem.</a>
  <p>