=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/errata33.html,v retrieving revision 1.51 retrieving revision 1.52 diff -c -r1.51 -r1.52 *** www/errata33.html 2014/03/31 03:12:47 1.51 --- www/errata33.html 2014/03/31 03:36:54 1.52 *************** *** 76,86 ****

- -

All architectures

! 022: SECURITY FIX: May 5, 2004
Pathname validation problems have been found in cvs(1), allowing malicious clients to create files outside the repository, allowing --- 76,84 ----
- ! 022: SECURITY FIX: May 5, 2004 All architectures
  Pathname validation problems have been found in cvs(1), allowing malicious clients to create files outside the repository, allowing *************** *** 92,98 **** A source code patch exists which remedies this problem.
- ! 021: RELIABILITY FIX: March 17, 2004
  A missing check for a NULL-pointer dereference has been found in ssl(3). A remote attacker can use the bug to cause an OpenSSL application to crash; --- 90,96 ---- A source code patch exists which remedies this problem.
- ! 021: RELIABILITY FIX: March 17, 2004 All architectures
  A missing check for a NULL-pointer dereference has been found in ssl(3). A remote attacker can use the bug to cause an OpenSSL application to crash; *************** *** 102,108 **** A source code patch exists which remedies this problem.
- ! 020: RELIABILITY FIX: March 17, 2004
  Defects in the payload validation and processing functions of isakmpd(8) have been discovered. An attacker could send malformed ISAKMP messages and --- 100,106 ---- A source code patch exists which remedies this problem.
- ! 020: RELIABILITY FIX: March 17, 2004 All architectures
  Defects in the payload validation and processing functions of isakmpd(8) have been discovered. An attacker could send malformed ISAKMP messages and *************** *** 113,119 **** A source code patch exists which remedies this problem.
- ! 019: SECURITY FIX: March 13, 2004
  Due to a bug in the parsing of Allow/Deny rules for httpd(8)'s access module, using IP addresses without a netmask on big endian 64-bit --- 111,117 ---- A source code patch exists which remedies this problem.
- ! 019: SECURITY FIX: March 13, 2004 All architectures
  Due to a bug in the parsing of Allow/Deny rules for httpd(8)'s access module, using IP addresses without a netmask on big endian 64-bit *************** *** 123,129 **** A source code patch exists which remedies this problem.
- ! 018: RELIABILITY FIX: March 8, 2004
  OpenBSD's TCP/IP stack did not impose limits on how many out-of-order TCP segments are queued in the system. An attacker could send out-of-order TCP segments and trick the system into using all --- 121,127 ---- A source code patch exists which remedies this problem.
- ! 018: RELIABILITY FIX: March 8, 2004 All architectures
  OpenBSD's TCP/IP stack did not impose limits on how many out-of-order TCP segments are queued in the system. An attacker could send out-of-order TCP segments and trick the system into using all *************** *** 133,139 **** A source code patch exists which remedies this problem.
- ! 017: RELIABILITY FIX: February 14, 2004
  Several buffer overflows exist in the code parsing font.aliases files in XFree86. Thanks to ProPolice, these cannot be exploited to gain privileges, but they can cause the X server to abort. --- 131,137 ---- A source code patch exists which remedies this problem.
- ! 017: RELIABILITY FIX: February 14, 2004 All architectures
  Several buffer overflows exist in the code parsing font.aliases files in XFree86. Thanks to ProPolice, these cannot be exploited to gain privileges, but they can cause the X server to abort. *************** *** 142,148 **** A source code patch exists which remedies this problem.
- ! 016: SECURITY FIX: February 8, 2004
  An IPv6 MTU handling problem exists that could be used by an attacker to cause a denial of service attack against hosts with reachable IPv6 TCP ports. --- 140,146 ---- A source code patch exists which remedies this problem.
- ! 016: SECURITY FIX: February 8, 2004 All architectures
  An IPv6 MTU handling problem exists that could be used by an attacker to cause a denial of service attack against hosts with reachable IPv6 TCP ports. *************** *** 151,157 **** A source code patch exists which remedies this problem.
- ! 015: SECURITY FIX: February 5, 2004
  A reference counting bug exists in the shmat(2) system call that could be used by an attacker to write to kernel memory --- 149,155 ---- A source code patch exists which remedies this problem.
- ! 015: SECURITY FIX: February 5, 2004 All architectures
  A reference counting bug exists in the shmat(2) system call that could be used by an attacker to write to kernel memory *************** *** 161,167 **** A source code patch exists which remedies this problem.
- ! 014: SECURITY FIX: January 15, 2004
  Several message handling flaws in isakmpd(8) have been reported by Thomas Walpuski. These allow an attacker to delete arbitrary SAs. --- 159,165 ---- A source code patch exists which remedies this problem.
- ! 014: SECURITY FIX: January 15, 2004 All architectures
  Several message handling flaws in isakmpd(8) have been reported by Thomas Walpuski. These allow an attacker to delete arbitrary SAs. *************** *** 170,176 **** A source code patch exists which remedies this problem.
- ! 013: RELIABILITY FIX: November 20, 2003
  An improper bounds check makes it possible for a local user to cause a crash by passing the semctl(2) and --- 168,174 ---- A source code patch exists which remedies this problem.
- ! 013: RELIABILITY FIX: November 20, 2003 All architectures
  An improper bounds check makes it possible for a local user to cause a crash by passing the semctl(2) and *************** *** 181,201 **** A source code patch exists which remedies this problem.
- ! 012: RELIABILITY FIX: November 20, 2003
  It is possible for a local user to cause a crash via sysctl(3) with certain arguments.
  A source code patch exists which remedies this problem.
- ! 010: RELIABILITY FIX: November 4, 2003
  It is possible for a local user to cause a system panic by executing a specially crafted binary with an invalid header.
  A source code patch exists which remedies this problem.
- ! 009: RELIABILITY FIX: October 29, 2003
  A user with write permission to httpd.conf or a .htaccess file can crash httpd(8) --- 179,199 ---- A source code patch exists which remedies this problem.
- ! 012: RELIABILITY FIX: November 20, 2003 All architectures
  It is possible for a local user to cause a crash via sysctl(3) with certain arguments.
  A source code patch exists which remedies this problem.
- ! 010: RELIABILITY FIX: November 4, 2003 All architectures
  It is possible for a local user to cause a system panic by executing a specially crafted binary with an invalid header.
  A source code patch exists which remedies this problem.
- ! 009: RELIABILITY FIX: October 29, 2003 All architectures
  A user with write permission to httpd.conf or a .htaccess file can crash httpd(8) *************** *** 206,219 **** A source code patch exists which remedies this problem.
- ! 008: RELIABILITY FIX: October 1, 2003
  It is possible for a local user to cause a system panic by flooding it with spoofed ARP requests.
  A source code patch exists which remedies this problem.
- ! 007: SECURITY FIX: October 1, 2003
  The use of certain ASN.1 encodings or malformed public keys may allow an attacker to mount a denial of service attack against applications linked with ssl(3). --- 204,217 ---- A source code patch exists which remedies this problem.
- ! 008: RELIABILITY FIX: October 1, 2003 All architectures
  It is possible for a local user to cause a system panic by flooding it with spoofed ARP requests.
  A source code patch exists which remedies this problem.
- ! 007: SECURITY FIX: October 1, 2003 All architectures
  The use of certain ASN.1 encodings or malformed public keys may allow an attacker to mount a denial of service attack against applications linked with ssl(3). *************** *** 222,228 **** A source code patch exists which remedies this problem.
- ! 006: SECURITY FIX: September 24, 2003
  Three cases of potential access to freed memory have been found in pf(4). At least one of them could be used to panic pf with active scrub rules remotely.
  --- 220,226 ---- A source code patch exists which remedies this problem.
- ! 006: SECURITY FIX: September 24, 2003 All architectures
  Three cases of potential access to freed memory have been found in pf(4). At least one of them could be used to panic pf with active scrub rules remotely.
  *************** *** 230,236 **** A source code patch exists which remedies this problem.
- ! 005: SECURITY FIX: September 17, 2003
  A buffer overflow in the address parsing in sendmail(8) may allow an attacker to gain root privileges.
  --- 228,234 ---- A source code patch exists which remedies this problem.
- ! 005: SECURITY FIX: September 17, 2003 All architectures
  A buffer overflow in the address parsing in sendmail(8) may allow an attacker to gain root privileges.
  *************** *** 240,246 **** problem.
- ! 004: SECURITY FIX: September 16, 2003
  All versions of OpenSSH's sshd prior to 3.7 contain a buffer management error. It is unclear whether or not this bug is exploitable.
  --- 238,244 ---- problem.
- ! 004: SECURITY FIX: September 16, 2003 All architectures
  All versions of OpenSSH's sshd prior to 3.7 contain a buffer management error. It is unclear whether or not this bug is exploitable.
  *************** *** 249,262 **** problem.
- ! 003: SECURITY FIX: September 10, 2003
  Root may be able to reduce the security level by taking advantage of an integer overflow when the semaphore limits are made very large.
  A source code patch exists which remedies this problem.
- ! 002: RELIABILITY FIX: August 20, 2003
  An improper bounds check in the semget(2) system call can allow a local user to cause a kernel panic.
  --- 247,260 ---- problem.
- ! 003: SECURITY FIX: September 10, 2003 All architectures
  Root may be able to reduce the security level by taking advantage of an integer overflow when the semaphore limits are made very large.
  A source code patch exists which remedies this problem.
- ! 002: RELIABILITY FIX: August 20, 2003 All architectures
  An improper bounds check in the semget(2) system call can allow a local user to cause a kernel panic.
  *************** *** 264,270 **** A source code patch exists which remedies this problem.
- ! 001: SECURITY FIX: August 4, 2003
  An off-by-one error exists in the C library function realpath(3). Since this same bug resulted in a root compromise in the wu-ftpd ftp server --- 262,268 ---- A source code patch exists which remedies this problem.
- ! 001: SECURITY FIX: August 4, 2003 All architectures
  An off-by-one error exists in the C library function realpath(3). Since this same bug resulted in a root compromise in the wu-ftpd ftp server