This is the OpenBSD 3.2 release errata & patch list:

The patches below are available in CVS via the OPENBSD_3_2 patch branch.

For more detailed information on how to install patches to OpenBSD, please consult the OpenBSD FAQ.

• 021: 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.

• 020: 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). This does not affect OpenSSH.
  A source code patch exists which remedies this problem.

• 019: 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.
  A source code patch exists which remedies this problem.

• 018: 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.
  A source code patch exists which remedies this problem. NOTE: this is the second revision of the patch that fixes an additional

• 017: 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.
  A source code patch exists which remedies this problem. NOTE: this is the second revision of the patch that fixes an additional problem.

• 016: SECURITY FIX: August 25, 2003   All architectures
  Fix for a potential security issue in sendmail(8) with respect to DNS maps. This only affects sendmail(8) configurations that use the "enhdnsbl" feature. The default OpenBSD sendmail(8) config does not use this.
  A source code patch exists which remedies this problem.

• 015: 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 it is possible that this bug may allow an attacker to gain escalated privileges on OpenBSD.
  A source code patch exists which remedies this problem.

• 014: SECURITY FIX: March 31, 2003   All architectures
  A buffer overflow in the address parsing in sendmail(8) may allow an attacker to gain root privileges.
  A source code patch exists which remedies this problem.

• 013: SECURITY FIX: March 24, 2003   All architectures
  The cryptographic weaknesses in the Kerberos v4 protocol can be exploited on Kerberos v5 as well.
  A source code patch exists which remedies this problem.

• 012: SECURITY FIX: March 19, 2003   All architectures
  OpenSSL is vulnerable to an extension of the ``Bleichenbacher'' attack designed by Czech researchers Klima, Pokorny and Rosa.
  A source code patch exists which remedies this problem.

• 011: SECURITY FIX: March 18, 2003   All architectures
  Various SSL and TLS operations in OpenSSL are vulnerable to timing attacks.
  A source code patch exists which remedies this problem.

• 010: SECURITY FIX: March 5, 2003   All architectures
  A fix for an lprm(1) bug made in 1996 contains an error that could lead to privilege escalation. For OpenBSD 3.2 the impact is limited since lprm(1) is setuid daemon, not setuid root.
  A source code patch exists which remedies this problem.

• 009: SECURITY FIX: March 3, 2003   All architectures
  A buffer overflow in the envelope comments processing in sendmail(8) may allow an attacker to gain root privileges.
  A source code patch exists which remedies this problem.

• 008: SECURITY FIX: February 25, 2003   All architectures
  httpd(8) leaks file inode numbers via ETag header as well as child PIDs in multipart MIME boundary generation. This could lead, for example, to NFS exploitation because it uses inode numbers as part of the file handle.
  A source code patch exists which fixes these two issues.

• 007: SECURITY FIX: February 22, 2003   All architectures
  In ssl(8) an information leak can occur via timing by performing a MAC computation even if incorrect block cipher padding has been found, this is a countermeasure. Also, check for negative sizes in memory allocation routines.
  A source code patch exists which fixes these two issues.

• 006: SECURITY FIX: January 20, 2003   All architectures
  A double free in cvs(1) could allow an attacker to execute code with the privileges of the user running cvs. This is only an issue when the cvs command is being run on a user's behalf as a different user. This means that, in most cases, the issue only exists for cvs configurations that use the pserver client/server connection method.
  A source code patch exists which remedies this problem.

• 005: SECURITY FIX: November 14, 2002   All architectures
  A buffer overflow in named(8) could allow an attacker to execute code with the privileges of named. On OpenBSD, named runs as a non-root user in a chrooted environment which mitigates the effects of this bug.
  A source code patch exists which remedies this problem.

• 004: RELIABILITY FIX: November 6, 2002   All architectures
  A logic error in the pool kernel memory allocator could cause memory corruption in low-memory situations, causing the system to crash.
  A source code patch exists which remedies this problem.

• 003: SECURITY FIX: November 6, 2002   All architectures
  An attacker can bypass the restrictions imposed by sendmail's restricted shell, smrsh(8), and execute arbitrary commands with the privileges of his own account.
  A source code patch exists which remedies this problem.

• 002: RELIABILITY FIX: November 6, 2002   All architectures
  Network bridges running pf with scrubbing enabled could cause mbuf corruption, causing the system to crash.
  A source code patch exists which remedies this problem.

• 001: SECURITY FIX: October 21, 2002   All architectures
  A buffer overflow can occur in the kadmind(8) daemon, leading to possible remote crash or exploit.
  A source code patch exists which remedies this problem.