===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata35.html,v
retrieving revision 1.53
retrieving revision 1.54
diff -c -r1.53 -r1.54
*** www/errata35.html 2014/10/02 14:34:45 1.53
--- www/errata35.html 2015/02/14 04:36:51 1.54
***************
*** 82,88 ****
! -
033: SECURITY FIX: April 28, 2005
All architectures
Fix a buffer overflow, memory leaks, and NULL pointer dereference in
--- 82,88 ----
! -
033: SECURITY FIX: April 28, 2005
All architectures
Fix a buffer overflow, memory leaks, and NULL pointer dereference in
***************
*** 95,101 ****
A source code patch exists which remedies this problem.
!
-
032: RELIABILITY FIX: April 4, 2005
All architectures
Handle an edge condition in
--- 95,101 ----
A source code patch exists which remedies this problem.
!
-
032: RELIABILITY FIX: April 4, 2005
All architectures
Handle an edge condition in
***************
*** 106,112 ****
A source code patch exists which remedies this problem.
!
-
031: SECURITY FIX: March 30, 2005
All architectures
Due to buffer overflows in
--- 106,112 ----
A source code patch exists which remedies this problem.
!
-
031: SECURITY FIX: March 30, 2005
All architectures
Due to buffer overflows in
***************
*** 120,126 ****
A source code patch exists which remedies this problem.
!
-
030: RELIABILITY FIX: March 30, 2005
All architectures
Bugs in the
--- 120,126 ----
A source code patch exists which remedies this problem.
!
-
030: RELIABILITY FIX: March 30, 2005
All architectures
Bugs in the
***************
*** 132,138 ****
A source code patch exists which remedies this problem.
!
-
029: SECURITY FIX: March 16, 2005
amd64 only
More stringent checking should be done in the
--- 132,138 ----
A source code patch exists which remedies this problem.
!
-
029: SECURITY FIX: March 16, 2005
amd64 only
More stringent checking should be done in the
***************
*** 143,149 ****
A source code patch exists which remedies this problem.
!
-
028: SECURITY FIX: February 28, 2005
i386 only
More stringent checking should be done in the
--- 143,149 ----
A source code patch exists which remedies this problem.
!
-
028: SECURITY FIX: February 28, 2005
i386 only
More stringent checking should be done in the
***************
*** 154,160 ****
A source code patch exists which remedies this problem.
!
-
027: RELIABILITY FIX: January 11, 2005
All architectures
A bug in the
--- 154,160 ----
A source code patch exists which remedies this problem.
!
-
027: RELIABILITY FIX: January 11, 2005
All architectures
A bug in the
***************
*** 167,173 ****
A source code patch exists which remedies this problem.
!
-
026: SECURITY FIX: January 12, 2005
All architectures
httpd(8)
--- 167,173 ----
A source code patch exists which remedies this problem.
!
-
026: SECURITY FIX: January 12, 2005
All architectures
httpd(8)
***************
*** 182,188 ****
A source code patch exists which remedies this problem.
!
-
025: RELIABILITY FIX: January 6, 2005
All architectures
The
--- 182,188 ----
A source code patch exists which remedies this problem.
!
-
025: RELIABILITY FIX: January 6, 2005
All architectures
The
***************
*** 194,200 ****
A source code patch exists which remedies this problem.
!
-
024: SECURITY FIX: December 14, 2004
All architectures
On systems running
--- 194,200 ----
A source code patch exists which remedies this problem.
!
-
024: SECURITY FIX: December 14, 2004
All architectures
On systems running
***************
*** 207,213 ****
A source code patch exists which remedies this problem.
!
-
023: RELIABILITY FIX: November 10, 2004
All architectures
Due to a bug in
--- 207,213 ----
A source code patch exists which remedies this problem.
!
-
023: RELIABILITY FIX: November 10, 2004
All architectures
Due to a bug in
***************
*** 221,227 ****
A source code patch exists which remedies this problem.
!
-
022: RELIABILITY FIX: November 10, 2004
All architectures
pppd(8)
--- 221,227 ----
A source code patch exists which remedies this problem.
!
-
022: RELIABILITY FIX: November 10, 2004
All architectures
pppd(8)
***************
*** 231,237 ****
A source code patch exists which remedies this problem.
!
-
021: RELIABILITY FIX: November 10, 2004
All architectures
BIND contains a bug which results in BIND trying to contact nameservers via IPv6, even in
--- 231,237 ----
A source code patch exists which remedies this problem.
!
-
021: RELIABILITY FIX: November 10, 2004
All architectures
BIND contains a bug which results in BIND trying to contact nameservers via IPv6, even in
***************
*** 241,247 ****
A source code patch exists which remedies this problem.
!
-
020: SECURITY FIX: September 20, 2004
All architectures
Eilko Bos reported that radius authentication, as implemented by
--- 241,247 ----
A source code patch exists which remedies this problem.
!
-
020: SECURITY FIX: September 20, 2004
All architectures
Eilko Bos reported that radius authentication, as implemented by
***************
*** 253,259 ****
A source code patch exists which remedies this problem.
!
-
019: SECURITY FIX: September 16, 2004
All architectures
Chris Evans reported several flaws (stack and integer overflows) in the
--- 253,259 ----
A source code patch exists which remedies this problem.
!
-
019: SECURITY FIX: September 16, 2004
All architectures
Chris Evans reported several flaws (stack and integer overflows) in the
***************
*** 267,273 ****
A source code patch exists which remedies this problem.
!
-
018: SECURITY FIX: September 10, 2004
All architectures
httpd(8)
--- 267,273 ----
A source code patch exists which remedies this problem.
!
-
018: SECURITY FIX: September 10, 2004
All architectures
httpd(8)
***************
*** 279,285 ****
A source code patch exists which remedies this problem.
!
-
017: RELIABILITY FIX: August 29, 2004
All architectures
Due to incorrect error handling in zlib an attacker could potentially cause a Denial
--- 279,285 ----
A source code patch exists which remedies this problem.
!
-
017: RELIABILITY FIX: August 29, 2004
All architectures
Due to incorrect error handling in zlib an attacker could potentially cause a Denial
***************
*** 290,296 ****
A source code patch exists which remedies this problem.
!
-
016: RELIABILITY FIX: August 26, 2004
All architectures
As
--- 290,296 ----
A source code patch exists which remedies this problem.
!
-
016: RELIABILITY FIX: August 26, 2004
All architectures
As
***************
*** 302,308 ****
A source code patch exists which remedies this problem.
!
-
015: RELIABILITY FIX: August 25, 2004
All architectures
Improved verification of ICMP errors in order to minimize the impact of ICMP attacks
--- 302,308 ----
A source code patch exists which remedies this problem.
!
-
015: RELIABILITY FIX: August 25, 2004
All architectures
Improved verification of ICMP errors in order to minimize the impact of ICMP attacks
***************
*** 313,319 ****
A source code patch exists which remedies this problem.
!
-
014: RELIABILITY FIX: July 25, 2004
All architectures
Under a certain network load the kernel can run out of stack space. This was
--- 313,319 ----
A source code patch exists which remedies this problem.
!
-
014: RELIABILITY FIX: July 25, 2004
All architectures
Under a certain network load the kernel can run out of stack space. This was
***************
*** 323,329 ****
A source code patch exists which remedies this problem.
!
-
013: SECURITY FIX: June 12, 2004
All architectures
Multiple vulnerabilities have been found in
--- 323,329 ----
A source code patch exists which remedies this problem.
!
-
013: SECURITY FIX: June 12, 2004
All architectures
Multiple vulnerabilities have been found in
***************
*** 337,343 ****
A source code patch exists which remedies this problem.
!
-
012: SECURITY FIX: June 10, 2004
All architectures
As
--- 337,343 ----
A source code patch exists which remedies this problem.
!
-
012: SECURITY FIX: June 10, 2004
All architectures
As
***************
*** 350,356 ****
A source code patch exists which remedies this problem.
!
-
011: SECURITY FIX: June 9, 2004
All architectures
Multiple remote vulnerabilities have been found in the
--- 350,356 ----
A source code patch exists which remedies this problem.
!
-
011: SECURITY FIX: June 9, 2004
All architectures
Multiple remote vulnerabilities have been found in the
***************
*** 361,367 ****
A source code patch exists which remedies this problem.
!
-
010: RELIABILITY FIX: June 9, 2004
All architectures
A FIFO bug was introduced in OpenBSD 3.5 that occurs when a FIFO is opened in
--- 361,367 ----
A source code patch exists which remedies this problem.
!
-
010: RELIABILITY FIX: June 9, 2004
All architectures
A FIFO bug was introduced in OpenBSD 3.5 that occurs when a FIFO is opened in
***************
*** 372,378 ****
A source code patch exists which remedies this problem.
!
-
009: SECURITY FIX: May 30, 2004
All architectures
A flaw in the Kerberos V
--- 372,378 ----
A source code patch exists which remedies this problem.
!
-
009: SECURITY FIX: May 30, 2004
All architectures
A flaw in the Kerberos V
***************
*** 387,393 ****
A source code patch exists which remedies this problem.
!
-
008: SECURITY FIX: May 26, 2004
All architectures
With the introduction of IPv6 code in
--- 387,393 ----
A source code patch exists which remedies this problem.
!
-
008: SECURITY FIX: May 26, 2004
All architectures
With the introduction of IPv6 code in
***************
*** 401,407 ****
A source code patch exists which remedies this problem.
!
-
007: SECURITY FIX: May 20, 2004
All architectures
A heap overflow in the
--- 401,407 ----
A source code patch exists which remedies this problem.
!
-
007: SECURITY FIX: May 20, 2004
All architectures
A heap overflow in the
***************
*** 413,419 ****
A source code patch exists which remedies this problem.
!
-
006: SECURITY FIX: May 13, 2004
All architectures
Check for integer overflow in procfs. Use of procfs is not recommended.
--- 413,419 ----
A source code patch exists which remedies this problem.
!
-
006: SECURITY FIX: May 13, 2004
All architectures
Check for integer overflow in procfs. Use of procfs is not recommended.
***************
*** 421,427 ****
A source code patch exists which remedies this problem.
!
-
005: RELIABILITY FIX: May 6, 2004
All architectures
Reply to in-window SYN with a rate-limited ACK.
--- 421,427 ----
A source code patch exists which remedies this problem.
!
-
005: RELIABILITY FIX: May 6, 2004
All architectures
Reply to in-window SYN with a rate-limited ACK.
***************
*** 429,435 ****
A source code patch exists which remedies this problem.
!
-
004: RELIABILITY FIX: May 5, 2004
All architectures
Restore the ability to negotiate tags/wide/sync with some SCSI controllers ( i.e.
--- 429,435 ----
A source code patch exists which remedies this problem.
!
-
004: RELIABILITY FIX: May 5, 2004
All architectures
Restore the ability to negotiate tags/wide/sync with some SCSI controllers ( i.e.
***************
*** 441,447 ****
A source code patch exists which remedies this problem.
!
-
003: RELIABILITY FIX: May 5, 2004
All architectures
Under load "recent model"
--- 441,447 ----
A source code patch exists which remedies this problem.
!
-
003: RELIABILITY FIX: May 5, 2004
All architectures
Under load "recent model"
***************
*** 451,457 ****
A source code patch exists which remedies this problem.
!
-
002: SECURITY FIX: May 5, 2004
All architectures
Pathname validation problems have been found in
--- 451,457 ----
A source code patch exists which remedies this problem.
!
-
002: SECURITY FIX: May 5, 2004
All architectures
Pathname validation problems have been found in
***************
*** 464,470 ****
A source code patch exists which remedies this problem.
!
-
001: BROKEN PACKAGE ON CD: May 4, 2004 macppc only
The powerpc autobook-1.3.tgz package found on CD2 has been found to be corrupt,
and will not extract.
--- 464,470 ----
A source code patch exists which remedies this problem.
!
-
001: BROKEN PACKAGE ON CD: May 4, 2004 macppc only
The powerpc autobook-1.3.tgz package found on CD2 has been found to be corrupt,
and will not extract.