===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata55.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -c -r1.30 -r1.31
*** www/errata55.html	2015/01/13 19:47:25	1.30
--- www/errata55.html	2015/02/14 04:36:51	1.31
***************
*** 83,89 ****
  
  <ul>
  
! <li><a name="001_icmp"></a>
  <font color="#009000"><strong>001: RELIABILITY FIX: March 15, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Memory corruption happens during
--- 83,89 ----
  
  <ul>
  
! <li id="001_icmp">
  <font color="#009000"><strong>001: RELIABILITY FIX: March 15, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Memory corruption happens during
***************
*** 93,99 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="002_openssl"></a>
  <font color="#009000"><strong>002: SECURITY FIX: April 8, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Missing bounds checking in OpenSSL's implementation of the TLS/DTLS
--- 93,99 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="002_openssl">
  <font color="#009000"><strong>002: SECURITY FIX: April 8, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Missing bounds checking in OpenSSL's implementation of the TLS/DTLS
***************
*** 103,109 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="003_ftp"></a>
  <font color="#009000"><strong>003: SECURITY FIX: April 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Missing hostname check for HTTPS connections in the
--- 103,109 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="003_ftp">
  <font color="#009000"><strong>003: SECURITY FIX: April 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Missing hostname check for HTTPS connections in the
***************
*** 114,120 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="004_openssl"></a>
  <font color="#009000"><strong>004: SECURITY FIX: April 12, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  A use-after-free race condition in OpenSSL's read buffer may permit an attacker
--- 114,120 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="004_openssl">
  <font color="#009000"><strong>004: SECURITY FIX: April 12, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  A use-after-free race condition in OpenSSL's read buffer may permit an attacker
***************
*** 124,130 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="005_openssl"></a>
  <font color="#009000"><strong>005: RELIABILITY FIX: May 1, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  An attacker can trigger generation of an SSL alert which could cause
--- 124,130 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="005_openssl">
  <font color="#009000"><strong>005: RELIABILITY FIX: May 1, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  An attacker can trigger generation of an SSL alert which could cause
***************
*** 134,140 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="006_libXfont"></a>
  <font color="#009000"><strong>006: SECURITY FIX: May 24, 2014</strong></font>
  &nbsp; <i>All architectures with X server</i><br>
  X Font Service Protocol & Font metadata file handling issues in libXfont
--- 134,140 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="006_libXfont">
  <font color="#009000"><strong>006: SECURITY FIX: May 24, 2014</strong></font>
  &nbsp; <i>All architectures with X server</i><br>
  X Font Service Protocol & Font metadata file handling issues in libXfont
***************
*** 149,155 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="007_sendmail"></a>
  <font color="#009000"><strong>007: SECURITY FIX: June 5, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Sendmail was not properly closing file descriptions before executing programs.
--- 149,155 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="007_sendmail">
  <font color="#009000"><strong>007: SECURITY FIX: June 5, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Sendmail was not properly closing file descriptions before executing programs.
***************
*** 160,166 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="008_openssl"></a>
  <font color="#009000"><strong>008: SECURITY FIX: June 6, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  This patch contains a number of SSL library fixes.
--- 160,166 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="008_openssl">
  <font color="#009000"><strong>008: SECURITY FIX: June 6, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  This patch contains a number of SSL library fixes.
***************
*** 169,175 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="009_dhcp"></a>
  <font color="#009000"><strong>009: RELIABILITY FIX: July 30, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Packets with illegal DHCP options can lead to memory exhaustion of
--- 169,175 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="009_dhcp">
  <font color="#009000"><strong>009: RELIABILITY FIX: July 30, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Packets with illegal DHCP options can lead to memory exhaustion of
***************
*** 181,187 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="010_openssl"></a>
  <font color="#009000"><strong>010: SECURITY FIX: August 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  This patch contains a number of SSL library fixes.
--- 181,187 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="010_openssl">
  <font color="#009000"><strong>010: SECURITY FIX: August 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  This patch contains a number of SSL library fixes.
***************
*** 190,196 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="011_nginx"></a>
  <font color="#009000"><strong>011: SECURITY FIX: October 1, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  nginx can reuse cached SSL sessions in unrelated contexts, allowing virtual
--- 190,196 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="011_nginx">
  <font color="#009000"><strong>011: SECURITY FIX: October 1, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  nginx can reuse cached SSL sessions in unrelated contexts, allowing virtual
***************
*** 201,207 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="012_openssl"></a>
  <font color="#009000"><strong>012: RELIABILITY FIX: October 20, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Two remotely triggerable memory leaks in OpenSSL can lead to a denial of
--- 201,207 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="012_openssl">
  <font color="#009000"><strong>012: RELIABILITY FIX: October 20, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Two remotely triggerable memory leaks in OpenSSL can lead to a denial of
***************
*** 211,217 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="013_kernexec"></a>
  <font color="#009000"><strong>013: RELIABILITY FIX: October 20, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Executable headers with an unaligned address will trigger a kernel panic.
--- 211,217 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="013_kernexec">
  <font color="#009000"><strong>013: RELIABILITY FIX: October 20, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Executable headers with an unaligned address will trigger a kernel panic.
***************
*** 220,226 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="014_pfctl"></a>
  <font color="#009000"><strong>014: RELIABILITY FIX: November 17, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  A PF rule using an IPv4 address
--- 220,226 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="014_pfctl">
  <font color="#009000"><strong>014: RELIABILITY FIX: November 17, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  A PF rule using an IPv4 address
***************
*** 232,238 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="015_asr"></a>
  <font color="#009000"><strong>015: RELIABILITY FIX: November 17, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Querying an invalid hostname with gethostbyname(3) could cause a NULL deref.
--- 232,238 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="015_asr">
  <font color="#009000"><strong>015: RELIABILITY FIX: November 17, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Querying an invalid hostname with gethostbyname(3) could cause a NULL deref.
***************
*** 241,247 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="016_pipex"></a>
  <font color="#009000"><strong>016: RELIABILITY FIX: December 5, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Several bugs were fixed that allowed a crash from remote when an active pipex
--- 241,247 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="016_pipex">
  <font color="#009000"><strong>016: RELIABILITY FIX: December 5, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Several bugs were fixed that allowed a crash from remote when an active pipex
***************
*** 251,257 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="017_pppoe"></a>
  <font color="#009000"><strong>017: RELIABILITY FIX: December 5, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  An incorrect memcpy call would result in corrupted MAC addresses when
--- 251,257 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="017_pppoe">
  <font color="#009000"><strong>017: RELIABILITY FIX: December 5, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  An incorrect memcpy call would result in corrupted MAC addresses when
***************
*** 261,267 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="018_virtio"></a>
  <font color="#009000"><strong>018: RELIABILITY FIX: December 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Several bugs in virtio(4) can lead to hangs with virtio devices,
--- 261,267 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="018_virtio">
  <font color="#009000"><strong>018: RELIABILITY FIX: December 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  Several bugs in virtio(4) can lead to hangs with virtio devices,
***************
*** 271,277 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="019_xserver"></a>
  <font color="#009000"><strong>019: SECURITY FIX: December 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  One year after Ilja van Sprundel discovered and reported a large number
--- 271,277 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="019_xserver">
  <font color="#009000"><strong>019: SECURITY FIX: December 9, 2014</strong></font>
  &nbsp; <i>All architectures</i><br>
  One year after Ilja van Sprundel discovered and reported a large number
***************
*** 284,290 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="020_libevent"></a>
  <font color="#009000"><strong>020: SECURITY FIX: January 13, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix CVE-2014-6272 in libevent 1.4 event buffer handling.  OpenBSD
--- 284,290 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="020_libevent">
  <font color="#009000"><strong>020: SECURITY FIX: January 13, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix CVE-2014-6272 in libevent 1.4 event buffer handling.  OpenBSD