Annotation of www/errata45.html, Revision 1.72
1.62 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.50 tj 5: <title>OpenBSD 4.5 Errata</title>
1.1 djm 6: <meta name="description" content="the OpenBSD CD errata page">
1.49 deraadt 7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.52 tb 9: <link rel="canonical" href="https://www.openbsd.org/errata45.html">
1.1 djm 10:
1.39 deraadt 11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.1 djm 16:
1.62 bentley 17: <h2 id=OpenBSD>
1.49 deraadt 18: <a href="index.html">
1.62 bentley 19: <i>Open</i><b>BSD</b></a>
20: 4.5 Errata
1.50 tj 21: </h2>
1.49 deraadt 22: <hr>
1.1 djm 23:
24: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
25: <br>
26: For errata on a certain release, click below:<br>
1.65 schwarze 27: <a href="errata20.html">2.0</a>,
1.1 djm 28: <a href="errata21.html">2.1</a>,
29: <a href="errata22.html">2.2</a>,
30: <a href="errata23.html">2.3</a>,
31: <a href="errata24.html">2.4</a>,
32: <a href="errata25.html">2.5</a>,
33: <a href="errata26.html">2.6</a>,
34: <a href="errata27.html">2.7</a>,
35: <a href="errata28.html">2.8</a>,
36: <a href="errata29.html">2.9</a>,
37: <a href="errata30.html">3.0</a>,
38: <a href="errata31.html">3.1</a>,
39: <a href="errata32.html">3.2</a>,
40: <a href="errata33.html">3.3</a>,
41: <a href="errata34.html">3.4</a>,
42: <a href="errata35.html">3.5</a>,
1.65 schwarze 43: <br>
1.1 djm 44: <a href="errata36.html">3.6</a>,
45: <a href="errata37.html">3.7</a>,
46: <a href="errata38.html">3.8</a>,
47: <a href="errata39.html">3.9</a>,
48: <a href="errata40.html">4.0</a>,
49: <a href="errata41.html">4.1</a>,
50: <a href="errata42.html">4.2</a>,
1.3 deraadt 51: <a href="errata43.html">4.3</a>,
1.10 deraadt 52: <a href="errata44.html">4.4</a>,
1.16 deraadt 53: <a href="errata46.html">4.6</a>,
1.26 deraadt 54: <a href="errata47.html">4.7</a>,
1.27 miod 55: <a href="errata48.html">4.8</a>,
1.28 nick 56: <a href="errata49.html">4.9</a>,
1.29 sthen 57: <a href="errata50.html">5.0</a>,
1.30 deraadt 58: <a href="errata51.html">5.1</a>,
1.31 deraadt 59: <a href="errata52.html">5.2</a>,
1.65 schwarze 60: <br>
1.32 deraadt 61: <a href="errata53.html">5.3</a>,
1.33 deraadt 62: <a href="errata54.html">5.4</a>,
1.38 jsg 63: <a href="errata55.html">5.5</a>,
1.42 deraadt 64: <a href="errata56.html">5.6</a>,
1.45 deraadt 65: <a href="errata57.html">5.7</a>,
1.46 deraadt 66: <a href="errata58.html">5.8</a>,
1.51 deraadt 67: <a href="errata59.html">5.9</a>,
1.54 tj 68: <a href="errata60.html">6.0</a>,
1.58 deraadt 69: <a href="errata61.html">6.1</a>,
1.59 deraadt 70: <a href="errata62.html">6.2</a>,
1.60 deraadt 71: <a href="errata63.html">6.3</a>,
1.61 deraadt 72: <a href="errata64.html">6.4</a>,
1.64 deraadt 73: <a href="errata65.html">6.5</a>,
1.66 deraadt 74: <a href="errata66.html">6.6</a>,
1.67 deraadt 75: <a href="errata67.html">6.7</a>,
1.69 deraadt 76: <a href="errata68.html">6.8</a>,
1.70 tj 77: <br>
1.71 deraadt 78: <a href="errata69.html">6.9</a>,
1.72 ! deraadt 79: <a href="errata70.html">7.0</a>,
! 80: <a href="errata71.html">7.1</a>.
1.1 djm 81: <hr>
82:
1.36 deraadt 83: <p>
1.54 tj 84: Patches for the OpenBSD base system are distributed as unified diffs.
85: Each patch contains usage instructions.
86: All the following patches are also available in one
87: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5.tar.gz">tar.gz file</a>
88: for convenience.
1.1 djm 89:
1.36 deraadt 90: <p>
1.54 tj 91: Patches for supported releases are also incorporated into the
1.55 tj 92: <a href="stable.html">-stable branch</a>.
1.36 deraadt 93:
1.1 djm 94: <hr>
95:
96: <ul>
1.22 jasper 97:
1.63 deraadt 98: <li id="p001_openssl">
99: <strong>001: RELIABILITY FIX: April 8, 2009</strong>
1.37 deraadt 100: <i>All architectures</i><br>
1.63 deraadt 101: The OpenSSL ASN.1 handling code could be forced to perform invalid memory
102: accesses through the use of certain invalid strings
103: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>)
104: or under certain error conditions triggerable by invalid ASN.1 structures
105: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0789">CVE-2009-0789</a>).
106: These vulnerabilities could be exploited to achieve a
107: denial-of-service. A more detailed description of these problems is available
108: in the
109: <a href="http://www.openssl.org/news/secadv_20090325.txt">OpenSSL security advisory</a>, but note that the other issue described there "Incorrect Error
110: Checking During CMS verification" relates to code not enabled in OpenBSD.
1.19 dlg 111: <br>
1.63 deraadt 112: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/001_openssl.patch">
1.36 deraadt 113: A source code patch exists which remedies this problem.</a>
1.19 dlg 114: <p>
115:
1.63 deraadt 116: <li id="p002_pf">
117: <strong>002: RELIABILITY FIX: April 11, 2009</strong>
1.37 deraadt 118: <i>All architectures</i><br>
1.63 deraadt 119: When pf attempts to perform translation on a specially crafted IP datagram,
120: a null pointer dereference will occur, resulting in a kernel panic.
121: In certain configurations this may be triggered by a remote attacker.
1.18 jasper 122: <br>
1.63 deraadt 123: Restricting translation rules to protocols that are specific to the IP version
124: in use, is an effective workaround until the patch can be installed. As an
125: example, for IPv4 nat/binat/rdr rules you can use:
126: <pre>
127: nat/rdr ... inet proto { tcp udp icmp } ...
128: </pre>
129: Or for IPv6 nat/binat/rdr rules you can use:
130: <pre>
131: nat/rdr ... inet6 proto { tcp udp icmp6 } ...
132: </pre>
133: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/002_pf.patch">
1.36 deraadt 134: A source code patch exists which remedies this problem.</a>
1.18 jasper 135: <p>
136:
1.63 deraadt 137: <li id="p003_bus_dma">
138: <strong>003: RELIABILITY FIX: April 24, 2009</strong>
139: <i>i386 only</i><br>
140: When DMA'able memory is mapped by device drivers, the
141: mapping flags and protection are partially uninitialized.
142: Depending on the calling context, this may cause devices to misbehave, like
143: <a href="https://man.openbsd.org/OpenBSD-4.5/audio.4">audio(4)</a>
144: to stutter, but other anomalies might be observed for other
145: device types.
1.17 jasper 146: <br>
1.63 deraadt 147: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/i386/003_bus_dma.patch">
1.36 deraadt 148: A source code patch exists which remedies this problem.</a>
1.17 jasper 149: <p>
150:
1.63 deraadt 151: <li id="p004_aucat">
152: <strong>004: RELIABILITY FIX: April 24, 2009</strong>
1.37 deraadt 153: <i>All architectures</i><br>
1.63 deraadt 154: In server mode when in full-duplex mode (the default)
155: <a href="https://man.openbsd.org/OpenBSD-4.5/aucat.1">aucat(1)</a>
156: will send each synchronization message twice, causing client applications
1.68 jsg 157: to think that buffer underruns are occurring. Depending on the
1.63 deraadt 158: application, this may cause the sound to stutter.
1.17 jasper 159: <br>
1.63 deraadt 160: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/004_aucat.patch">
1.36 deraadt 161: A source code patch exists which remedies this problem.</a>
1.17 jasper 162: <p>
163:
1.63 deraadt 164: <li id="p005_audio">
165: <strong>005: RELIABILITY FIX: April 24, 2009</strong>
1.37 deraadt 166: <i>All architectures</i><br>
1.63 deraadt 167: On very high system load, an audio interrupt may occur while the
168: audio process is filling audio ring buffers. This triggers bogus
169: (and useless) correction code in the
170: <a href="https://man.openbsd.org/OpenBSD-4.5/audio.4">audio(4)</a>
171: driver causing the audio application to go out of sync, and in turn causing
172: continuous stuttering until the application is restarted.
1.15 sthen 173: <br>
1.63 deraadt 174: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/005_audio.patch">
1.36 deraadt 175: A source code patch exists which remedies this problem.</a>
1.15 sthen 176: <p>
177:
1.63 deraadt 178: <li id="p006_perl">
179: <strong>006: RELIABILITY FIX: June 24, 2009</strong>
1.37 deraadt 180: <i>All architectures</i><br>
1.63 deraadt 181: An off-by-one error in the inflate function in Zlib.xs in the
182: Compress::Raw::Zlib perl module before 2.017 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1391">CVE-2009-1391</a>),
183: as used in AMaViS, SpamAssassin, and possibly other products,
184: allows context-dependent attackers to cause a denial of service
185: (hang or crash) via a crafted zlib compressed stream that
186: triggers a heap-based buffer overflow.
1.14 sthen 187: <br>
1.63 deraadt 188: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/006_perl_zlib.patch">
1.36 deraadt 189: A source code patch exists which remedies this problem.</a>
1.14 sthen 190: <p>
191:
1.63 deraadt 192: <li id="p007_bind">
193: <strong>007: RELIABILITY FIX: July 29, 2009</strong>
1.37 deraadt 194: <i>All architectures</i><br>
1.63 deraadt 195: A vulnerability has been found in BIND's named server
196: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).
197: An attacker could crash a server with a specially crafted dynamic update message to a
198: zone for which the server is master.
1.13 deraadt 199: <br>
1.63 deraadt 200: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/007_bind.patch">
1.36 deraadt 201: A source code patch exists which remedies this problem.</a>
1.13 deraadt 202: <p>
203:
1.56 tb 204: <li id="p008_xmm">
1.62 bentley 205: <strong>008: RELIABILITY FIX: October 05, 2009</strong>
1.37 deraadt 206: <i>i386 only</i><br>
1.12 jsing 207: XMM exceptions are not correctly handled resulting in a kernel panic.
208: <br>
1.53 tb 209: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/i386/008_xmm.patch">
1.36 deraadt 210: A source code patch exists which remedies this problem.</a>
1.12 jsing 211: <p>
212:
1.63 deraadt 213: <li id="p009_getsockopt">
214: <strong>009: RELIABILITY FIX: October 28, 2009</strong>
1.37 deraadt 215: <i>All architectures</i><br>
1.63 deraadt 216: getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
217: IP_IPCOMP_LEVEL will crash the system.
1.9 jasper 218: <br>
1.63 deraadt 219: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/009_getsockopt.patch">
1.36 deraadt 220: A source code patch exists which remedies this problem.</a>
1.9 jasper 221: <p>
222:
1.63 deraadt 223: <li id="p010_openssl">
224: <strong>010: SECURITY FIX: November 26, 2009</strong>
1.37 deraadt 225: <i>All architectures</i><br>
1.63 deraadt 226: The SSL/TLS protocol is subject to man-in-the-middle attacks related to
227: renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).
228: OpenSSL permitted this protocol feature by default and had no way to
229: disable it.
1.8 fkr 230: <br>
1.63 deraadt 231: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/010_openssl.patch">
1.36 deraadt 232: A source code patch exists which remedies this problem.</a>
1.8 fkr 233: <p>
234:
1.63 deraadt 235: <li id="p011_ptrace">
236: <strong>011: RELIABILITY FIX: January 29, 2010</strong>
237: <i>All architectures</i><br>
238: By using ptrace(2) on an ancestor process, a loop in the process tree
239: could be created, violating assumptions in other parts of the kernel
240: and resulting in infinite loops.
241: <br>
242: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/011_ptrace.patch">
243: A source code patch exists which remedies this problem.</a>
244: <p>
1.1 djm 245:
1.63 deraadt 246: <li id="p012_openssl">
247: <strong>012: SECURITY FIX: March 12, 2010</strong>
1.37 deraadt 248: <i>All architectures</i><br>
1.63 deraadt 249: OpenSSL is susceptible to a buffer overflow due to a failure
250: to check for NULL returns from bn_wexpand function calls.
1.7 ratchov 251: <br>
1.63 deraadt 252: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/012_openssl.patch">
1.36 deraadt 253: A source code patch exists which remedies this problem.</a>
1.7 ratchov 254: <p>
255:
1.63 deraadt 256: <li id="p013_ftpd">
257: <strong>013: RELIABILITY FIX: March 12, 2010</strong>
1.37 deraadt 258: <i>All architectures</i><br>
1.63 deraadt 259: Due to a null pointer dereference, it would be possible to crash ftpd when
260: handling glob(3)'ing requests. This is non-exploitable.
1.7 ratchov 261: <br>
1.63 deraadt 262: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/013_ftpd.patch">
1.36 deraadt 263: A source code patch exists which remedies this problem.</a>
1.7 ratchov 264: <p>
265:
1.63 deraadt 266: <li id="p014_kerberos">
267: <strong>014: RELIABILITY FIX: March 31, 2010</strong>
268: <i>All architectures</i><br>
269: When decrypting packets, the internal decryption functions were not
270: paranoid enough in checking for underruns, which could potentially
271: lead to crashes.
1.7 ratchov 272: <br>
1.63 deraadt 273: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/014_kerberos.patch">
1.36 deraadt 274: A source code patch exists which remedies this problem.</a>
1.7 ratchov 275: <p>
276:
1.63 deraadt 277: <li id="p015_mpi">
278: <strong>015: RELIABILITY FIX: April 4, 2010</strong>
1.37 deraadt 279: <i>All architectures</i><br>
1.63 deraadt 280: When updating sensors showing the state of RAID volumes
281: <a href="https://man.openbsd.org/OpenBSD-4.5/mpi.4">mpi(4)</a>
282: allocates temporary memory and then returns it to the kernel as
283: device memory.
284: This causes kernel memory usage to be misrepresented, eventually
285: leading to a denial of service when a resource limit is apparently
286: reached.
1.5 sthen 287: <br>
1.63 deraadt 288: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/015_mpi.patch">
1.36 deraadt 289: A source code patch exists which remedies this problem.</a>
1.4 sthen 290: <p>
291:
1.63 deraadt 292: <li id="p016_openssl">
293: <strong>016: SECURITY FIX: April 14, 2010</strong>
1.37 deraadt 294: <i>All architectures</i><br>
1.63 deraadt 295: In TLS connections, certain incorrectly formatted records can cause
296: an OpenSSL client or server to crash due to a read attempt at NULL.
1.1 djm 297: <br>
1.63 deraadt 298: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/016_openssl.patch">
1.36 deraadt 299: A source code patch exists which remedies this problem.</a>
1.1 djm 300: <p>
301:
302: </ul>
303:
1.41 tedu 304: <hr>