| version 1.39, 2014/03/31 03:12:47 |
version 1.40, 2014/03/31 16:02:48 |
|
|
| |
|
| <ul> |
<ul> |
| <li><a name="016_getsockopt"></a> |
<li><a name="016_getsockopt"></a> |
| <font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font> |
| |
<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. |
| <br> |
<br> |
|
|
| <p> |
<p> |
| |
|
| <li><a name="015_xmm"></a> |
<li><a name="015_xmm"></a> |
| <font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font> <i>i386 only</i><br> |
<font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font> |
| |
<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> |
| <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/i386/015_xmm.patch"> |
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/i386/015_xmm.patch"> |
|
|
| <p> |
<p> |
| |
|
| <li><a name="014_bind"></a> |
<li><a name="014_bind"></a> |
| <font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font> |
| |
<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>). |
| An attacker could crash a server with a specially crafted dynamic update message to a |
An attacker could crash a server with a specially crafted dynamic update message to a |
|
|
| <p> |
<p> |
| |
|
| <li><a name="013_pf"></a> |
<li><a name="013_pf"></a> |
| <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font> |
| |
<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. |
|
|
| <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> <i>All architectures</i><br> |
<font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font> |
| |
<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>) |
|
|
| <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> <i>All architectures</i><br> |
<font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font> |
| |
<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 |
|
|
| <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> <i>All architectures</i><br> |
<font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font> |
| |
<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> |
|
|
| <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> <i>All architectures</i><br> |
<font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font> |
| |
<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 |
|
|
| <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> <i>All architectures</i><br> |
<font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font> |
| |
<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. |
|
|
| <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> <i>All architectures</i><br> |
<font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font> |
| |
<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" |
|
|
| <p> |
<p> |
| |
|
| <li><a name="006_dhcpd"></a> |
<li><a name="006_dhcpd"></a> |
| <font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font> |
| |
<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 |
| accepting DHCP offers. |
accepting DHCP offers. |
|
|
| <p> |
<p> |
| |
|
| <li><a name="005_pglistalloc"></a> |
<li><a name="005_pglistalloc"></a> |
| <font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font> |
| |
<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. |
| <br> |
<br> |
|
|
| <p> |
<p> |
| |
|
| <li><a name="004_httpd"></a> |
<li><a name="004_httpd"></a> |
| <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font> |
| |
<i>All architectures</i><br> |
| Fix |
Fix |
| <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=httpd&sektion=8">httpd(8)</a>'s |
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=httpd&sektion=8">httpd(8)</a>'s |
| mod_proxy module which is broken on 64-bit architectures. Due to the bug this |
mod_proxy module which is broken on 64-bit architectures. Due to the bug this |
|
|
| <p> |
<p> |
| |
|
| <li><a name="003_tcpinput"></a> |
<li><a name="003_tcpinput"></a> |
| <font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font> |
| |
<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 |
| if being received on a socket in the TIME_WAIT state. |
if being received on a socket in the TIME_WAIT state. |
|
|
| <p> |
<p> |
| |
|
| <li><a name="002_vr"></a> |
<li><a name="002_vr"></a> |
| <font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font> |
| |
<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. |
| <br> |
<br> |
|
|
| <p> |
<p> |
| |
|
| <li><a name="001_ndp"></a> |
<li><a name="001_ndp"></a> |
| <font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font> <i>All architectures</i><br> |
<font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font> |
| |
<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 |
![[BACK]](/icons/back.gif){kind=icon}
Return to errata44.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www