OpenBSD 4.3 Errata

For errata on a certain release, click below:
2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5,
3.6, 3.7, 3.8, 3.9, 4.0, 4.1, 4.2, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, 5.0, 5.1, 5.2,
5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8,
6.9, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5.

Patches for the OpenBSD base system are distributed as unified diffs. Each patch contains usage instructions. All the following patches are also available in one tar.gz file for convenience.

Patches for supported releases are also incorporated into the -stable branch.

001: SECURITY FIX: March 30, 2008 All architectures
sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) ForceCommand directive was in effect, allowing users with write access to this file to execute arbitrary commands. This behaviour was documented, but was an unsafe default and an extra hassle for administrators.
A source code patch exists which remedies this problem.
002: SECURITY FIX: April 3, 2008 All architectures
Avoid possible hijacking of X11-forwarded connections with sshd(8) by refusing to listen on a port unless all address families bind successfully.
A source code patch exists which remedies this problem.
003: SECURITY FIX: July 15, 2008 All architectures
Multiple vulnerabilities have been discovered in X.Org.
RENDER Extension heap buffer overflow, RENDER Extension crash, RENDER Extension memory corruption, MIT-SHM arbitrary memory read, RECORD and Security extensions memory corruption. CVE-2008-2360, CVE-2008-2361, CVE-2008-2362, CVE-2008-1379, CVE-2008-1377.
A source code patch exists which remedies this problem.
004: SECURITY FIX: July 23, 2008 All architectures
2nd revision, July 23, 2008
A vulnerability has been found with BIND. An attacker could use this vulnerability to poison the cache of a recursive resolving name server. CVE-2008-1447.
A source code patch exists which remedies this problem.
005: RELIABILITY FIX: July 29, 2008 All architectures
Some kinds of IPv6 usage would leak kernel memory (in particular, this path was exercised by the named(8) patch for port randomization). Since INET6 is enabled by default, this condition affects all systems.
A source code patch exists which remedies this problem.
006: SECURITY FIX: October 2, 2008 All architectures
The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor solicitation requests maybe allowing a nearby attacker to intercept traffic. The attacker must have IPv6 connectivity to the same router as their target for this vulnerability to be exploited. CVE-2008-2476.
A source code patch exists which remedies this problem.
007: SECURITY FIX: January 9, 2009 All architectures
The OpenSSL libraries did not correctly check the return value from certain verification functions, allowing validation to be bypassed and permitting a remote attacker to conduct a "man in the middle attack" against SSL/TLS connections if the server is configured with a DSA or ECDSA certificate. CVE-2008-5077.
A source code patch exists which remedies this problem.
008: SECURITY FIX: January 14, 2009 All architectures
named(8) did not correctly check the return value of a DSA verification function, potentially allowing bypass of verification of DNSSEC DSA signatures. CVE-2009-0025.
A source code patch exists which remedies this problem.
009: RELIABILITY FIX: January 30, 2009 All architectures
Upon reception of an invalid update with 4-byte AS attributes, bgpd - adhering to the RFCs - closed the session to the neighbor. This error in the specification allowed 3rd parties to close remote BGP sessions. In the worst case Internet connectivity could be lost.
A source code patch exists which remedies this problem.
010: RELIABILITY FIX: February 18, 2009 All architectures
bgpd(8) did not correctly prepend its own AS to very long AS paths, causing the process to terminate because of the resulting corrupt path.
A source code patch exists which remedies this problem.
011: SECURITY FIX: February 22, 2009 All architectures
sudo(8) may allow a user listed in the sudoers file to run a command as a different user than their access rule specifies when a Unix group is used in the RunAs portion of the rule. The bug only manifests when the user being granted privileges is also a member of the group in the RunAs portion of the rule.
A source code patch exists which remedies this problem.
012: RELIABILITY FIX: April 8, 2009 All architectures
The OpenSSL ASN.1 handling code could be forced to perform invalid memory accesses through the use of certain invalid strings (CVE-2009-0590) or under certain error conditions triggerable by invalid ASN.1 structures (CVE-2009-0789). These vulnerabilities could be exploited to achieve a denial-of-service. A more detailed description of these problems is available in the OpenSSL security advisory, but note that the other issue described there "Incorrect Error Checking During CMS verification" relates to code not enabled in OpenBSD.
A source code patch exists which remedies this problem.
013: RELIABILITY FIX: April 11, 2009 All architectures
When pf attempts to perform translation on a specially crafted IP datagram, a null pointer dereference will occur, resulting in a kernel panic. In certain configurations this may be triggered by a remote attacker.
Restricting translation rules to protocols that are specific to the IP version in use, is an effective workaround until the patch can be installed. As an example, for IPv4 nat/binat/rdr rules you can use:
```
    nat/rdr ... inet proto { tcp udp icmp } ...
```
Or for IPv6 nat/binat/rdr rules you can use:
```
    nat/rdr ... inet6 proto { tcp udp icmp6 } ...
```
A source code patch exists which remedies this problem.