version 1.46, 2014/10/02 14:34:45 |
version 1.47, 2015/02/14 04:36:51 |
|
|
|
|
<ul> |
<ul> |
|
|
<li><a name="015_ndp"></a> |
<li id="015_ndp"> |
<font color="#009000"><strong>015: SECURITY FIX: October 2, 2008</strong></font> |
<font color="#009000"><strong>015: 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="014_pcb"></a> |
<li id="014_pcb"> |
<font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2008</strong></font> |
<font color="#009000"><strong>014: 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="013_bind"></a> |
<li id="013_bind"> |
<font color="#009000"><strong>013: SECURITY FIX: July 23, 2008</strong></font> |
<font color="#009000"><strong>013: 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="012_xorg2"></a> |
<li id="012_xorg2"> |
<font color="#009000"><strong>012: SECURITY FIX: July 15, 2008</strong></font> |
<font color="#009000"><strong>012: 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="011_openssh2"></a> |
<li id="011_openssh2"> |
<font color="#009000"><strong>011: SECURITY FIX: April 3, 2008</strong></font> |
<font color="#009000"><strong>011: 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="010_openssh"></a> |
<li id="010_openssh"> |
<font color="#009000"><strong>010: SECURITY FIX: March 30, 2008</strong></font> |
<font color="#009000"><strong>010: 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> |
|
|
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_ppp"></a> |
<li id="009_ppp"> |
<font color="#009000"><strong>009: SECURITY FIX: March 7, 2008</strong></font> |
<font color="#009000"><strong>009: SECURITY FIX: March 7, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Buffer overflow in ppp command prompt parsing.<br> |
Buffer overflow in ppp command prompt parsing.<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="008_ip6rthdr"></a> |
<li id="008_ip6rthdr"> |
<font color="#009000"><strong>008: RELIABILITY FIX: February 25, 2008</strong></font> |
<font color="#009000"><strong>008: RELIABILITY FIX: February 25, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Malformed IPv6 routing headers can cause a kernel panic.<br> |
Malformed IPv6 routing headers can cause a kernel panic.<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="007_tcprespond"></a> |
<li id="007_tcprespond"> |
<font color="#009000"><strong>007: RELIABILITY FIX: February 22, 2008</strong></font> |
<font color="#009000"><strong>007: RELIABILITY FIX: February 22, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Incorrect assumptions in tcp_respond can lead to a kernel panic.<br> |
Incorrect assumptions in tcp_respond can lead to a kernel panic.<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="006_xorg"></a> |
<li id="006_xorg"> |
<font color="#009000"><strong>006: SECURITY FIX: February 8, 2008</strong></font> |
<font color="#009000"><strong>006: SECURITY FIX: February 8, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
<strong>2nd revision, February 10, 2008</strong><br> |
<strong>2nd revision, February 10, 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="005_ifrtlabel"></a> |
<li id="005_ifrtlabel"> |
<font color="#009000"><strong>005: RELIABILITY FIX: January 11, 2008</strong></font> |
<font color="#009000"><strong>005: RELIABILITY FIX: January 11, 2008</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
A missing NULL pointer check can lead to a kernel panic.<br> |
A missing NULL pointer check can lead to a kernel panic.<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="004_pf"></a> |
<li id="004_pf"> |
<font color="#009000"><strong>004: RELIABILITY FIX: November 27, 2007</strong></font> |
<font color="#009000"><strong>004: RELIABILITY FIX: November 27, 2007</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
A memory leak in pf can lead to machine lockups.<br> |
A memory leak in pf can lead to machine lockups.<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_i386_boot"></a> |
<li id="003_i386_boot"> |
<font color="#009000"><strong>003: CD BOOT FAILURE ON OLDER COMPUTERS : October 30, 2007</strong></font> |
<font color="#009000"><strong>003: CD BOOT FAILURE ON OLDER COMPUTERS : October 30, 2007</strong></font> |
<i>i386 only</i><br> |
<i>i386 only</i><br> |
Some older BIOSes are unable to boot CD1 (ie. the commercial release sold |
Some older BIOSes are unable to boot CD1 (ie. the commercial release sold |
|
|
|
|
<p> |
<p> |
|
|
<li><a name="002_openssl"></a> |
<li id="002_openssl"> |
<font color="#009000"><strong>002: SECURITY FIX: October 10, 2007</strong></font> |
<font color="#009000"><strong>002: SECURITY FIX: October 10, 2007</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
The SSL_get_shared_ciphers() function in OpenSSL contains an off-by-one overflow.<br> |
The SSL_get_shared_ciphers() function in OpenSSL contains an off-by-one overflow.<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="001_dhcpd"></a> |
<li id="001_dhcpd"> |
<font color="#009000"><strong>001: SECURITY FIX: October 8, 2007</strong></font> |
<font color="#009000"><strong>001: SECURITY FIX: October 8, 2007</strong></font> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Malicious DHCP clients could cause dhcpd(8) to corrupt its stack<br> |
Malicious DHCP clients could cause dhcpd(8) to corrupt its stack<br> |