! 020: SECURITY FIX: July 21, 2005All architectures
A buffer overflow has been found in
compress(3)
--- 86,92 ----
! 020: SECURITY FIX: July 21, 2005All architectures
A buffer overflow has been found in
compress(3)
***************
*** 100,106 ****
! 019: SECURITY FIX: July 6, 2005All architectures
A buffer overflow has been found in
compress(3)
--- 98,104 ----
! 019: SECURITY FIX: July 6, 2005All architectures
A buffer overflow has been found in
compress(3)
***************
*** 111,122 ****
! 018: SECURITY FIX: June 20, 2005All architectures
Due to a race condition in its command pathname handling, a user with
sudo(8)
privileges may be able to run arbitrary commands if the user's entry
! is followed by an entry that grants sudo ALL privileges to
another user.
--- 109,120 ----
! 017: RELIABILITY FIX: June 15, 2005All architectures
As discovered by Stefan Miltchev calling
getsockopt(2)
***************
*** 137,143 ****
! 016: SECURITY FIX: April 28, 2005All architectures
Fix a buffer overflow, memory leaks, and NULL pointer dereference in
cvs(1)
--- 135,141 ----
! 016: SECURITY FIX: April 28, 2005All architectures
Fix a buffer overflow, memory leaks, and NULL pointer dereference in
cvs(1)
***************
*** 150,156 ****
! 015: RELIABILITY FIX: April 4, 2005All architectures
Handle an edge condition in
tcp(4)
--- 148,154 ----
! 015: RELIABILITY FIX: April 4, 2005All architectures
Handle an edge condition in
tcp(4)
***************
*** 161,167 ****
! 014: SECURITY FIX: March 30, 2005All architectures
Due to buffer overflows in
telnet(1),
--- 159,165 ----
! 014: SECURITY FIX: March 30, 2005All architectures
Due to buffer overflows in
telnet(1),
***************
*** 176,182 ****
! 013: RELIABILITY FIX: March 30, 2005All architectures
Bugs in the
tcp(4)
--- 174,180 ----
! 013: RELIABILITY FIX: March 30, 2005All architectures
Bugs in the
tcp(4)
***************
*** 188,195 ****
! 012: SECURITY FIX: March 16, 2005
! amd64 only
More stringent checking should be done in the
copy(9)
functions to prevent their misuse.
--- 186,193 ----
! 012: SECURITY FIX: March 16, 2005
! amd64 only
More stringent checking should be done in the
copy(9)
functions to prevent their misuse.
***************
*** 199,206 ****
! 011: SECURITY FIX: February 28, 2005
! i386 only
More stringent checking should be done in the
copy(9)
functions to prevent their misuse.
--- 197,204 ----
! 011: SECURITY FIX: February 28, 2005
! i386 only
More stringent checking should be done in the
copy(9)
functions to prevent their misuse.
***************
*** 210,216 ****
! 010: RELIABILITY FIX: January 11, 2005All architectures
A bug in the
tcp(4)
--- 208,214 ----
! 010: RELIABILITY FIX: January 11, 2005All architectures
A bug in the
tcp(4)
***************
*** 223,229 ****
! 009: SECURITY FIX: January 12, 2005All architectures httpd(8)
's mod_include module fails to properly validate the length of
--- 221,227 ----
! 009: SECURITY FIX: January 12, 2005All architectures httpd(8)
's mod_include module fails to properly validate the length of
***************
*** 238,244 ****
! 008: RELIABILITY FIX: January 6, 2005All architectures
The
getcwd(3)
--- 236,242 ----
! 008: RELIABILITY FIX: January 6, 2005All architectures
The
getcwd(3)
***************
*** 250,256 ****
! 007: SECURITY FIX: December 14, 2004All architectures
On systems running
isakmpd(8)
--- 248,254 ----
! 007: SECURITY FIX: December 14, 2004All architectures
On systems running
isakmpd(8)
***************
*** 264,270 ****
! 006: RELIABILITY FIX: November 21, 2004All architectures
Fix for transmit side breakage on macppc and mbuf leaks with
xl(4).
--- 262,268 ----
! 006: RELIABILITY FIX: November 21, 2004All architectures
Fix for transmit side breakage on macppc and mbuf leaks with
xl(4).
***************
*** 274,280 ****
! 005: RELIABILITY FIX: November 21, 2004All architectures
Wrong calculation of NAT-D payloads may cause interoperability problems between
isakmpd(8)
--- 272,278 ----
! 005: RELIABILITY FIX: November 21, 2004All architectures
Wrong calculation of NAT-D payloads may cause interoperability problems between
isakmpd(8)
***************
*** 285,291 ****
! 004: RELIABILITY FIX: November 10, 2004All architectures
Due to a bug in
lynx(1)
--- 283,289 ----
! 004: RELIABILITY FIX: November 10, 2004All architectures
Due to a bug in
lynx(1)
***************
*** 300,306 ****
! 003: RELIABILITY FIX: November 10, 2004All architectures pppd(8)
contains a bug that allows an attacker to crash his own connection, but it cannot
--- 298,304 ----
! 003: RELIABILITY FIX: November 10, 2004All architectures pppd(8)
contains a bug that allows an attacker to crash his own connection, but it cannot
***************
*** 311,317 ****
! 002: RELIABILITY FIX: November 10, 2004All architectures
BIND contains a bug which results in BIND trying to contact nameservers via IPv6, even in
cases where IPv6 connectivity is non-existent. This results in unnecessary timeouts and
--- 309,315 ----
! 002: RELIABILITY FIX: November 10, 2004All architectures
BIND contains a bug which results in BIND trying to contact nameservers via IPv6, even in
cases where IPv6 connectivity is non-existent. This results in unnecessary timeouts and
***************
*** 322,328 ****
! 001: RELIABILITY FIX: November 10, 2004All architectures
Fix detection of tape blocksize during device open. Corrects problem with
restore(8).
--- 320,326 ----
! 001: RELIABILITY FIX: November 10, 2004All architectures
Fix detection of tape blocksize during device open. Corrects problem with
restore(8).
***************
*** 334,339 ****