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

Diff for /www/errata44.html between version 1.64 and 1.65

version 1.64, 2019/04/02 12:46:57 version 1.65, 2019/05/27 22:55:20
Line 1 
Line 1 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">  <!doctype html>
 <html>  <html lang=en id=errata>
 <head>  <meta charset=utf-8>
   
 <title>OpenBSD 4.4 Errata</title>  <title>OpenBSD 4.4 Errata</title>
 <meta name="description" content="the OpenBSD CD errata page">  <meta name="description" content="the OpenBSD CD errata page">
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">  
 <meta name="viewport" content="width=device-width, initial-scale=1">  <meta name="viewport" content="width=device-width, initial-scale=1">
 <link rel="stylesheet" type="text/css" href="openbsd.css">  <link rel="stylesheet" type="text/css" href="openbsd.css">
 <link rel="canonical" href="https://www.openbsd.org/errata44.html">  <link rel="canonical" href="https://www.openbsd.org/errata44.html">
 </head>  
   
 <!--  <!--
                         IMPORTANT REMINDER                          IMPORTANT REMINDER
         IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE          IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
 -->  -->
   
 <body bgcolor="#ffffff" text="#000000" link="#23238E">  
   
 <h2>  <h2 id=OpenBSD>
 <a href="index.html">  <a href="index.html">
 <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>  <i>Open</i><b>BSD</b></a>
 <font color="#e00000">4.4 Errata</font>  4.4 Errata
 </h2>  </h2>
 <hr>  <hr>
   
Line 87 
Line 85 
   
 <ul>  <ul>
 <li id="p016_getsockopt">  <li id="p016_getsockopt">
 <font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font>  <strong>016: RELIABILITY FIX: October 28, 2009</strong>
 &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,
 IP_IPCOMP_LEVEL will crash the system.  IP_IPCOMP_LEVEL will crash the system.
Line 97 
Line 95 
 <p>  <p>
   
 <li id="p015_xmm">  <li id="p015_xmm">
 <font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font>  <strong>015: RELIABILITY FIX: October 05, 2009</strong>
 &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.
 <br>  <br>
Line 106 
Line 104 
 <p>  <p>
   
 <li id="p014_bind">  <li id="p014_bind">
 <font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font>  <strong>014: RELIABILITY FIX: July 29, 2009</strong>
 &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
 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).  (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).
Line 118 
Line 116 
 <p>  <p>
   
 <li id="p013_pf">  <li id="p013_pf">
 <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font>  <strong>013: RELIABILITY FIX: April 11, 2009</strong>
 &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,
 a null pointer dereference will occur, resulting in a kernel panic.  a null pointer dereference will occur, resulting in a kernel panic.
Line 139 
Line 137 
 <p>  <p>
   
 <li id="p012_openssl">  <li id="p012_openssl">
 <font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font>  <strong>012: RELIABILITY FIX: April 8, 2009</strong>
 &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
 accesses through the use of certain invalid strings  accesses through the use of certain invalid strings
Line 157 
Line 155 
 <p>  <p>
   
 <li id="p011_sudo">  <li id="p011_sudo">
 <font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font>  <strong>011: SECURITY FIX: February 22, 2009</strong>
 &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
 as a different user than their access rule specifies when a Unix  as a different user than their access rule specifies when a Unix
Line 170 
Line 168 
 <p>  <p>
   
 <li id="p010_bgpd">  <li id="p010_bgpd">
 <font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font>  <strong>010: RELIABILITY FIX: February 18, 2009</strong>
 &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
 the process to terminate because of the resulting corrupt path.  the process to terminate because of the resulting corrupt path.
Line 180 
Line 178 
 <p>  <p>
   
 <li id="p009_bgpd">  <li id="p009_bgpd">
 <font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font>  <strong>009: RELIABILITY FIX: January 30, 2009</strong>
 &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 -
 adhering to the RFCs - closed the session to the neighbor.  adhering to the RFCs - closed the session to the neighbor.
Line 193 
Line 191 
 <p>  <p>
   
 <li id="p008_bind">  <li id="p008_bind">
 <font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font>  <strong>008: SECURITY FIX: January 14, 2009</strong>
 &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
 function, potentially allowing bypass of verification of DNSSEC DSA  function, potentially allowing bypass of verification of DNSSEC DSA
Line 205 
Line 203 
 <p>  <p>
   
 <li id="p007_openssl">  <li id="p007_openssl">
 <font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font>  <strong>007: SECURITY FIX: January 9, 2009</strong>
 &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
 certain verification functions, allowing validation to be bypassed and  certain verification functions, allowing validation to be bypassed and
Line 219 
Line 217 
 <p>  <p>
   
 <li id="p006_dhcpd">  <li id="p006_dhcpd">
 <font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font>  <strong>006: RELIABILITY FIX: November 19, 2008</strong>
 &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
 DHCP clients such as Solaris/OpenSolaris and some embedded routers not  DHCP clients such as Solaris/OpenSolaris and some embedded routers not
Line 230 
Line 228 
 <p>  <p>
   
 <li id="p005_pglistalloc">  <li id="p005_pglistalloc">
 <font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font>  <strong>005: RELIABILITY FIX: November 7, 2008</strong>
 &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
 accessing an array out of its bounds, when physical memory is exhausted.  accessing an array out of its bounds, when physical memory is exhausted.
Line 240 
Line 238 
 <p>  <p>
   
 <li id="p004_httpd">  <li id="p004_httpd">
 <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font>  <strong>004: RELIABILITY FIX: November 6, 2008</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Fix  Fix
 <a href="https://man.openbsd.org/OpenBSD-4.4/httpd.8">httpd(8)</a>'s  <a href="https://man.openbsd.org/OpenBSD-4.4/httpd.8">httpd(8)</a>'s
Line 253 
Line 251 
 <p>  <p>
   
 <li id="p003_tcpinput">  <li id="p003_tcpinput">
 <font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font>  <strong>003: RELIABILITY FIX: November 6, 2008</strong>
 &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
 can result in TCP connections between two IPs being reset instead of accepted  can result in TCP connections between two IPs being reset instead of accepted
Line 264 
Line 262 
 <p>  <p>
   
 <li id="p002_vr">  <li id="p002_vr">
 <font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font>  <strong>002: RELIABILITY FIX: November 2, 2008</strong>
 &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)
 driver to panic under heavy load if the RX path runs out of mbufs.  driver to panic under heavy load if the RX path runs out of mbufs.
Line 274 
Line 272 
 <p>  <p>
   
 <li id="p001_ndp">  <li id="p001_ndp">
 <font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font>  <strong>001: SECURITY FIX: November 2, 2008</strong>
 &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
 solicitation requests maybe allowing a nearby attacker to intercept traffic.  solicitation requests maybe allowing a nearby attacker to intercept traffic.
Line 289 
Line 287 
 </ul>  </ul>
   
 <hr>  <hr>
   
 </body>  
 </html>  

Legend:
Removed from v.1.64  
changed lines
  Added in v.1.65