version 1.43, 2014/10/02 14:34:45 |
version 1.44, 2015/02/14 04:36:51 |
|
|
|
|
<ul> |
<ul> |
|
|
<li><a name="013_pf"></a> |
<li id="013_pf"> |
<font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font> |
<font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font> |
<i>All architectures</i><br> |
<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 source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
|
|
<li><a name="012_openssl"></a> |
<li id="012_openssl"> |
<font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font> |
<font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font> |
<i>All architectures</i><br> |
<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 |
|
|
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="011_sudo"></a> |
<li id="011_sudo"> |
<font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font> |
<font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font> |
<i>All architectures</i><br> |
<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 |
|
|
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="010_bgpd"></a> |
<li id="010_bgpd"> |
<font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font> |
<font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font> |
<i>All architectures</i><br> |
<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 |
|
|
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="009_bgpd"></a> |
<li id="009_bgpd"> |
<font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font> |
<font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font> |
<i>All architectures</i><br> |
<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 - |
|
|
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="008_bind"></a> |
<li id="008_bind"> |
<font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font> |
<font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font> |
<i>All architectures</i><br> |
<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 |
|
|
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="007_openssl"></a> |
<li id="007_openssl"> |
<font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font> |
<font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font> |
<i>All architectures</i><br> |
<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 |
|
|
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="006_ndp"></a> |
<li id="006_ndp"> |
<font color="#009000"><strong>006: SECURITY FIX: October 2, 2008</strong></font> |
<font color="#009000"><strong>006: SECURITY FIX: October 2, 2008</strong></font> |
<i>All architectures</i><br> |
<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 |
|
|
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="005_pcb"></a> |
<li id="005_pcb"> |
<font color="#009000"><strong>005: RELIABILITY FIX: July 29, 2008</strong></font> |
<font color="#009000"><strong>005: RELIABILITY FIX: July 29, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Some kinds of IPv6 usage would leak kernel memory (in particular, this path |
Some kinds of IPv6 usage would leak kernel memory (in particular, this path |
|
|
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="004_bind"></a> |
<li id="004_bind"> |
<font color="#009000"><strong>004: SECURITY FIX: July 23, 2008</strong></font> |
<font color="#009000"><strong>004: SECURITY FIX: July 23, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
<strong>2nd revision, July 23, 2008</strong><br> |
<strong>2nd revision, July 23, 2008</strong><br> |
|
|
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_xorg"></a> |
<li id="003_xorg"> |
<font color="#009000"><strong>003: SECURITY FIX: July 15, 2008</strong></font> |
<font color="#009000"><strong>003: SECURITY FIX: July 15, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Multiple vulnerabilities have been discovered in X.Org.<br> |
Multiple vulnerabilities have been discovered in X.Org.<br> |
|
|
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="002_openssh2"></a> |
<li id="002_openssh2"> |
<font color="#009000"><strong>002: SECURITY FIX: April 3, 2008</strong></font> |
<font color="#009000"><strong>002: SECURITY FIX: April 3, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Avoid possible hijacking of X11-forwarded connections with sshd(8) |
Avoid possible hijacking of X11-forwarded connections with sshd(8) |
|
|
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="001_openssh"></a> |
<li id="001_openssh"> |
<font color="#009000"><strong>001: SECURITY FIX: March 30, 2008</strong></font> |
<font color="#009000"><strong>001: SECURITY FIX: March 30, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) <em>ForceCommand</em> |
sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) <em>ForceCommand</em> |