Annotation of www/errata43.html, Revision 1.47
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 4.3 errata</title>
5: <meta name="resource-type" content="document">
6: <meta name="description" content="the OpenBSD CD errata page">
7: <meta name="keywords" content="openbsd,cd,errata">
8: <meta name="distribution" content="global">
9: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.47 ! sthen 10: <link rel="canonical" href="http://www.openbsd.org/errata43.html">
1.1 deraadt 11: </head>
12:
1.43 deraadt 13: <!--
14: IMPORTANT REMINDER
15: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
16: -->
17:
1.1 deraadt 18: <body bgcolor="#ffffff" text="#000000" link="#23238E">
19:
20: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.43 deraadt 21: <h2><font color="#e00000">
22: OpenBSD 4.3 errata
1.1 deraadt 23: </font></h2>
24:
25: <hr>
26: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
27: <br>
28: For errata on a certain release, click below:<br>
29: <a href="errata21.html">2.1</a>,
30: <a href="errata22.html">2.2</a>,
31: <a href="errata23.html">2.3</a>,
32: <a href="errata24.html">2.4</a>,
33: <a href="errata25.html">2.5</a>,
34: <a href="errata26.html">2.6</a>,
35: <a href="errata27.html">2.7</a>,
36: <a href="errata28.html">2.8</a>,
37: <a href="errata29.html">2.9</a>,
38: <a href="errata30.html">3.0</a>,
39: <a href="errata31.html">3.1</a>,
40: <a href="errata32.html">3.2</a>,
41: <a href="errata33.html">3.3</a>,
42: <a href="errata34.html">3.4</a>,
43: <a href="errata35.html">3.5</a>,
44: <a href="errata36.html">3.6</a>,
1.9 deraadt 45: <br>
1.1 deraadt 46: <a href="errata37.html">3.7</a>,
47: <a href="errata38.html">3.8</a>,
48: <a href="errata39.html">3.9</a>,
49: <a href="errata40.html">4.0</a>,
50: <a href="errata41.html">4.1</a>,
1.9 deraadt 51: <a href="errata42.html">4.2</a>,
1.22 deraadt 52: <a href="errata44.html">4.4</a>,
1.26 deraadt 53: <a href="errata45.html">4.5</a>,
1.27 deraadt 54: <a href="errata46.html">4.6</a>,
1.29 deraadt 55: <a href="errata47.html">4.7</a>,
1.31 miod 56: <a href="errata48.html">4.8</a>,
1.32 nick 57: <a href="errata49.html">4.9</a>,
1.33 sthen 58: <a href="errata50.html">5.0</a>,
1.34 deraadt 59: <a href="errata51.html">5.1</a>,
1.35 deraadt 60: <a href="errata52.html">5.2</a>,
1.36 deraadt 61: <a href="errata53.html">5.3</a>,
1.39 deraadt 62: <br>
1.37 deraadt 63: <a href="errata54.html">5.4</a>,
1.42 jsg 64: <a href="errata55.html">5.5</a>,
1.46 deraadt 65: <a href="errata56.html">5.6</a>,
66: <a href="errata57.html">5.7</a>.
1.1 deraadt 67: <br>
68: <hr>
69:
1.28 sthen 70: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3.tar.gz">
1.1 deraadt 71: You can also fetch a tar.gz file containing all the following patches</a>.
72: This file is updated once a day.
1.40 deraadt 73: <p>
1.1 deraadt 74:
1.40 deraadt 75: The patches below are available in CVS via the
1.1 deraadt 76: <code>OPENBSD_4_3</code> <a href="stable.html">patch branch</a>.
1.40 deraadt 77: <p>
1.1 deraadt 78:
79: For more detailed information on how to install patches to OpenBSD, please
80: consult the <a href="./faq/faq10.html#Patches">OpenBSD FAQ</a>.
1.40 deraadt 81: <p>
82:
1.1 deraadt 83: <hr>
84:
85: <ul>
86:
1.44 bentley 87: <li id="013_pf">
1.41 deraadt 88: <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font>
89: <i>All architectures</i><br>
1.23 sthen 90: When pf attempts to perform translation on a specially crafted IP datagram,
91: a null pointer dereference will occur, resulting in a kernel panic.
92: In certain configurations this may be triggered by a remote attacker.
1.24 sthen 93: <br>
1.23 sthen 94: Restricting translation rules to protocols that are specific to the IP version
95: in use, is an effective workaround until the patch can be installed. As an
96: example, for IPv4 nat/binat/rdr rules you can use:
97: <pre>
98: nat/rdr ... inet proto { tcp udp icmp } ...
99: </pre>
100: Or for IPv6 nat/binat/rdr rules you can use:
101: <pre>
102: nat/rdr ... inet6 proto { tcp udp icmp6 } ...
103: </pre>
1.28 sthen 104: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/013_pf.patch">
1.40 deraadt 105: A source code patch exists which remedies this problem.</a>
1.23 sthen 106: <p>
107:
1.44 bentley 108: <li id="012_openssl">
1.41 deraadt 109: <font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font>
110: <i>All architectures</i><br>
1.20 djm 111: The OpenSSL ASN.1 handling code could be forced to perform invalid memory
1.25 tobias 112: accesses through the use of certain invalid strings
1.20 djm 113: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>)
114: or under certain error conditions triggerable by invalid ASN.1 structures
115: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0789">CVE-2009-0789</a>).
116: These vulnerabilities could be exploited to achieve a
117: denial-of-service. A more detailed description of these problems is available
118: in the
119: <a href="http://www.openssl.org/news/secadv_20090325.txt">OpenSSL security advisory</a>, but note that the other issue described there "Incorrect Error
120: Checking During CMS verification" relates to code not enabled in OpenBSD.
121: <br>
1.28 sthen 122: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/012_openssl.patch">
1.40 deraadt 123: A source code patch exists which remedies this problem.</a>
1.20 djm 124: <p>
125:
1.44 bentley 126: <li id="011_sudo">
1.41 deraadt 127: <font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font>
128: <i>All architectures</i><br>
1.19 millert 129: sudo(8) may allow a user listed in the sudoers file to run a command
130: as a different user than their access rule specifies when a Unix
131: group is used in the RunAs portion of the rule. The bug only manifests
132: when the user being granted privileges is also a member of the group
133: in the RunAs portion of the rule.
134: <br>
1.28 sthen 135: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/011_sudo.patch">
1.40 deraadt 136: A source code patch exists which remedies this problem.</a>
1.19 millert 137: <p>
138:
1.44 bentley 139: <li id="010_bgpd">
1.41 deraadt 140: <font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font>
141: <i>All architectures</i><br>
1.18 claudio 142: bgpd(8) did not correctly prepend its own AS to very long AS paths, causing
143: the process to terminate because of the resulting corrupt path.
144: <br>
1.28 sthen 145: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/010_bgpd.patch">
1.40 deraadt 146: A source code patch exists which remedies this problem.</a>
1.18 claudio 147: <p>
148:
1.44 bentley 149: <li id="009_bgpd">
1.41 deraadt 150: <font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font>
151: <i>All architectures</i><br>
1.16 claudio 152: Upon reception of an invalid update with 4-byte AS attributes, bgpd -
153: adhering to the RFCs - closed the session to the neighbor.
154: This error in the specification allowed 3rd parties to close remote BGP
155: sessions.
156: In the worst case Internet connectivity could be lost.
157: <br>
1.28 sthen 158: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/009_bgpd.patch">
1.40 deraadt 159: A source code patch exists which remedies this problem.</a>
1.16 claudio 160: <p>
161:
1.44 bentley 162: <li id="008_bind">
1.41 deraadt 163: <font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font>
164: <i>All architectures</i><br>
1.14 djm 165: named(8) did not correctly check the return value of a DSA verification
166: function, potentially allowing bypass of verification of DNSSEC DSA
167: signatures.
168: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0025">CVE-2009-0025</a>.
169: <br>
1.28 sthen 170: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/008_bind.patch">
1.40 deraadt 171: A source code patch exists which remedies this problem.</a>
1.14 djm 172: <p>
173:
1.44 bentley 174: <li id="007_openssl">
1.41 deraadt 175: <font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font>
176: <i>All architectures</i><br>
1.13 djm 177: The OpenSSL libraries did not correctly check the return value from
1.17 miod 178: certain verification functions, allowing validation to be bypassed and
1.13 djm 179: permitting a remote attacker to conduct a "man in the middle attack"
180: against SSL/TLS connections if the server is configured with a DSA or ECDSA
181: certificate.
182: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5077">CVE-2008-5077</a>.
183: <br>
1.28 sthen 184: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/007_openssl.patch">
1.40 deraadt 185: A source code patch exists which remedies this problem.</a>
1.13 djm 186: <p>
187:
1.44 bentley 188: <li id="006_ndp">
1.41 deraadt 189: <font color="#009000"><strong>006: SECURITY FIX: October 2, 2008</strong></font>
190: <i>All architectures</i><br>
1.11 brad 191: The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor
192: solicitation requests maybe allowing a nearby attacker to intercept traffic.
193: The attacker must have IPv6 connectivity to the same router as their target for
194: this vulnerability to be exploited.
1.12 brad 195: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2476">CVE-2008-2476</a>.
1.11 brad 196: <br>
1.28 sthen 197: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/006_ndp.patch">
1.40 deraadt 198: A source code patch exists which remedies this problem.</a>
1.11 brad 199: <p>
200:
1.44 bentley 201: <li id="005_pcb">
1.41 deraadt 202: <font color="#009000"><strong>005: RELIABILITY FIX: July 29, 2008</strong></font>
203: <i>All architectures</i><br>
1.37 deraadt 204: Some kinds of IPv6 usage would leak kernel memory (in particular, this path
205: was exercised by the named(8) patch for port randomization). Since INET6 is
1.7 jdixon 206: enabled by default, this condition affects all systems.
207: <br>
1.28 sthen 208: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/005_pcb.patch">
1.40 deraadt 209: A source code patch exists which remedies this problem.</a>
1.7 jdixon 210: <p>
211:
1.44 bentley 212: <li id="004_bind">
1.41 deraadt 213: <font color="#009000"><strong>004: SECURITY FIX: July 23, 2008</strong></font>
214: <i>All architectures</i><br>
1.6 brad 215: <strong>2nd revision, July 23, 2008</strong><br>
1.5 brad 216: A vulnerability has been found with BIND. An attacker could use this vulnerability
217: to poison the cache of a recursive resolving name server.
218: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1447">CVE-2008-1447</a>.
219: <br>
1.28 sthen 220: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/004_bind.patch">
1.40 deraadt 221: A source code patch exists which remedies this problem.</a>
1.5 brad 222: <p>
223:
1.44 bentley 224: <li id="003_xorg">
1.41 deraadt 225: <font color="#009000"><strong>003: SECURITY FIX: July 15, 2008</strong></font>
226: <i>All architectures</i><br>
1.4 brad 227: Multiple vulnerabilities have been discovered in X.Org.<br>
228: RENDER Extension heap buffer overflow,
229: RENDER Extension crash,
230: RENDER Extension memory corruption,
231: MIT-SHM arbitrary memory read,
232: RECORD and Security extensions memory corruption.
1.5 brad 233: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2360">CVE-2008-2360</a>,
234: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2361">CVE-2008-2361</a>,
235: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2362">CVE-2008-2362</a>,
236: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1379">CVE-2008-1379</a>,
237: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1377">CVE-2008-1377</a>.
1.4 brad 238: <br>
1.28 sthen 239: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/003_xorg.patch">
1.40 deraadt 240: A source code patch exists which remedies this problem.</a>
1.4 brad 241: <p>
242:
1.44 bentley 243: <li id="002_openssh2">
1.41 deraadt 244: <font color="#009000"><strong>002: SECURITY FIX: April 3, 2008</strong></font>
245: <i>All architectures</i><br>
1.3 brad 246: Avoid possible hijacking of X11-forwarded connections with sshd(8)
247: by refusing to listen on a port unless all address families bind
248: successfully.<br>
1.28 sthen 249: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/002_openssh2.patch">
1.40 deraadt 250: A source code patch exists which remedies this problem.</a>
1.3 brad 251: <p>
252:
1.44 bentley 253: <li id="001_openssh">
1.41 deraadt 254: <font color="#009000"><strong>001: SECURITY FIX: March 30, 2008</strong></font>
255: <i>All architectures</i><br>
1.2 brad 256: sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) <em>ForceCommand</em>
257: directive was in effect, allowing users with write access to this file to
258: execute arbitrary commands. This behaviour was documented, but was an unsafe
259: default and an extra hassle for administrators.<br>
1.28 sthen 260: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/001_openssh.patch">
1.40 deraadt 261: A source code patch exists which remedies this problem.</a>
1.2 brad 262: <p>
1.1 deraadt 263:
264: </ul>
265:
1.45 tedu 266: <hr>
267:
1.1 deraadt 268: </body>
269: </html>