Annotation of www/errata23.html, Revision 1.65
1.28 naddy 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1 deraadt 2: <html>
3: <head>
1.12 deraadt 4: <title>OpenBSD 2.3 errata</title>
1.1 deraadt 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">
1.31 henning 9: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.1 deraadt 10: </head>
11:
1.32 david 12: <body bgcolor="#ffffff" text="#000000" link="#23238E">
1.1 deraadt 13:
1.23 jsyn 14: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.28 naddy 15: <h2><font color="#0000e0">
1.4 espie 16: This is the OpenBSD 2.3 release errata & patch list:
1.1 deraadt 17:
18: </font></h2>
19:
20: <hr>
1.13 jason 21: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.25 deraadt 22: <br>
1.26 deraadt 23: For errata on a certain release, click below:<br>
1.25 deraadt 24: <a href="errata21.html">2.1</a>,
25: <a href="errata22.html">2.2</a>,
26: <a href="errata24.html">2.4</a>,
27: <a href="errata25.html">2.5</a>,
28: <a href="errata26.html">2.6</a>,
29: <a href="errata27.html">2.7</a>,
30: <a href="errata28.html">2.8</a>,
31: <a href="errata29.html">2.9</a>,
32: <a href="errata30.html">3.0</a>,
33: <a href="errata31.html">3.1</a>,
1.29 deraadt 34: <a href="errata32.html">3.2</a>,
1.30 david 35: <a href="errata33.html">3.3</a>,
1.34 david 36: <a href="errata34.html">3.4</a>,
1.35 miod 37: <a href="errata35.html">3.5</a>,
1.36 deraadt 38: <a href="errata36.html">3.6</a>,
1.60 deraadt 39: <a href="errata37.html">3.7</a>,
1.45 deraadt 40: <br>
1.38 deraadt 41: <a href="errata38.html">3.8</a>,
1.39 deraadt 42: <a href="errata39.html">3.9</a>,
1.40 deraadt 43: <a href="errata40.html">4.0</a>,
1.42 merdely 44: <a href="errata41.html">4.1</a>,
1.44 deraadt 45: <a href="errata42.html">4.2</a>,
1.45 deraadt 46: <a href="errata43.html">4.3</a>,
1.47 deraadt 47: <a href="errata44.html">4.4</a>,
1.48 deraadt 48: <a href="errata45.html">4.5</a>,
1.49 deraadt 49: <a href="errata46.html">4.6</a>,
1.51 deraadt 50: <a href="errata47.html">4.7</a>,
1.52 miod 51: <a href="errata48.html">4.8</a>,
1.53 nick 52: <a href="errata49.html">4.9</a>,
1.54 sthen 53: <a href="errata50.html">5.0</a>,
1.55 deraadt 54: <a href="errata51.html">5.1</a>,
1.56 deraadt 55: <a href="errata52.html">5.2</a>,
1.57 deraadt 56: <a href="errata53.html">5.3</a>,
1.60 deraadt 57: <br>
1.58 deraadt 58: <a href="errata54.html">5.4</a>,
1.65 ! jsg 59: <a href="errata55.html">5.5</a>,
! 60: <a href="errata56.html">5.6</a>.
1.25 deraadt 61: <br>
1.1 deraadt 62: <hr>
63:
1.50 sthen 64: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3.tar.gz">
1.1 deraadt 65: You can also fetch a tar.gz file containing all the following patches</a>.
66: This file is updated once a day.
1.61 deraadt 67: <p>
1.1 deraadt 68:
1.61 deraadt 69: The patches below are available in CVS via the
70: <code>OPENBSD_2_3</code> <a href="stable.html">patch branch</a>.
1.14 ericj 71: <p>
1.61 deraadt 72:
1.27 deraadt 73: For more detailed information on how to install patches to OpenBSD, please
1.61 deraadt 74: consult the <a href="./faq/faq10.html#Patches">OpenBSD FAQ</a>.
75: <p>
1.14 ericj 76:
1.1 deraadt 77: <hr>
78:
79: <ul>
1.31 henning 80: <li><a name="bootpd"></a>
1.64 deraadt 81: <font color="#009000"><strong>SECURITY FIX</strong></font>
82: <i>All architectures</i><br>
1.5 deraadt 83: A remotely exploitable problem exists in bootpd(8). bootpd is disabled
84: by default, but some people may actually be using it.
1.50 sthen 85: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/bootpd.patch">
1.61 deraadt 86: A source code patch exists which remedies this problem.</a>
87: This is the second version of the patch.
1.5 deraadt 88: <p>
1.31 henning 89: <li><a name="tcpfix"></a>
1.64 deraadt 90: <font color="#009000"><strong>SECURITY FIX</strong></font>
91: <i>All architectures</i><br>
1.2 deraadt 92: A remote machine lockup problem exists in the TCP decoding code.
1.50 sthen 93: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/tcpfix.patch">
1.2 deraadt 94: A source code patch exists which remedies this problem.</a>
95: <p>
1.31 henning 96: <li><a name="atapi"></a>
1.64 deraadt 97: <font color="#009000"><strong>HARDWARE SUPPORT</strong></font>
98: <i>All architectures</i><br>
1.1 deraadt 99: Some ATAPI cdroms which do not support the full mandatory command set,
100: (e.g. ATAPI_READ_CD_CAPACITY) do not work with the acd(4) driver.
101: A patch is
1.50 sthen 102: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">
1.1 deraadt 103: available here.</a>
104: <p>
1.31 henning 105: <li><a name="chpass"></a>
1.64 deraadt 106: <font color="#009000"><strong>SECURITY FIX</strong></font>
107: <i>All architectures</i><br>
1.1 deraadt 108: Chpass(1) has a file descriptor leak which allows an
109: attacker to modify /etc/master.passwd.
1.50 sthen 110: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch">
1.1 deraadt 111: A source code patch exists which remedies this problem.</a>
112: <p>
1.31 henning 113: <li><a name="resid"></a>
1.64 deraadt 114: <font color="#009000"><strong>RELIABILITY FIX</strong></font>
115: <i>All architectures</i><br>
1.43 tobias 116: Calling readv(2) with iov_len < 0 or > INT_MAX would result in a
1.1 deraadt 117: kernel panic. This is the third revision of this patch.
1.50 sthen 118: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch">
1.1 deraadt 119: A source code patch exists which remedies this problem.</a>
120: <p>
1.31 henning 121: <li><a name="inetd"></a>
1.64 deraadt 122: <font color="#009000"><strong>SECURITY FIX</strong></font>
123: <i>All architectures</i><br>
1.1 deraadt 124: Inetd had a file descriptor leak. A patch is
1.50 sthen 125: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch">
1.1 deraadt 126: available here.</a>
127: <p>
1.31 henning 128: <li><a name="unionfs"></a>
1.64 deraadt 129: <font color="#009000"><strong>BUG FIX</strong></font>
130: <i>All architectures</i><br>
1.1 deraadt 131: As shipped, unionfs had some serious problems.
1.50 sthen 132: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch">
1.1 deraadt 133: A patch is available to solve this</a>.
134: <p>
1.31 henning 135: <li><a name="fdalloc"></a>
1.64 deraadt 136: <font color="#009000"><strong>SECURITY FIX</strong></font>
137: <i>All architectures</i><br>
1.1 deraadt 138: Some non-allocated file descriptors have implied uses according to
139: system libraries, and hence setuid and setgid processes should not
140: be executed with these descriptors unallocated. A patch which forces
141: setuid and setgid processes to have some descriptors in fd slots
1.58 deraadt 142: 0, 1, and 2 is
1.50 sthen 143: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">
1.1 deraadt 144: available here.</a>
145: <p>
1.31 henning 146: <li><a name="resolver"></a>
1.64 deraadt 147: <font color="#009000"><strong>SECURITY FIX</strong></font>
148: <i>All architectures</i><br>
1.3 deraadt 149: A benign looking buffer overflow in the resolver routines was re-introduced
150: accidentally. The previously fixed behaviour is more correct. A patch
151: to fix this is
1.50 sthen 152: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">
1.3 deraadt 153: available here.</a>
154: <p>
1.31 henning 155: <li><a name="xlib"></a>
1.64 deraadt 156: <font color="#009000"><strong>SECURITY FIX</strong></font>
157: <i>All architectures</i><br>
1.1 deraadt 158: Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
159: libraries. These affect xterm and all other setuid-root programs that
160: use these libraries. The problems are associated with buffer overflows
161: in code that processes user-supplied data. The Xt library problems
162: include those fixed in TOG's recent public patch 3 for X11R6.3. All
163: releases of XFree86 up to and including 3.3.2 patch 1 and the version
164: distributed with OpenBSD are vulnerable to some or all of these
165: problems.
166: These problems are fixed in XFree86 patch 2.
1.50 sthen 167: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/XFree86-3.3.2.2.patch">
1.1 deraadt 168: The 2nd source patch</a> for these problems, specifically adapted to the
169: OpenBSD 2.3 X11 tree, is available now.
170: <p>
1.31 henning 171: <li><a name="kill"></a>
1.64 deraadt 172: <font color="#009000"><strong>SECURITY FIX</strong></font>
173: <i>All architectures</i><br>
1.1 deraadt 174: The kill(2) system call previously would permit a large set of signals to
175: be delivered to setuid or setgid processes. If such processes were using
176: those signals in dubious ways, this could have resulted in security
177: problems of various kinds.
1.50 sthen 178: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/kill.patch">
1.1 deraadt 179: The fourth revision of a source code patch which solves the problem is
180: available.</a>
181: <p>
1.31 henning 182: <li><a name="immutable"></a>
1.64 deraadt 183: <font color="#009000"><strong>SECURITY FIX</strong></font>
184: <i>All architectures</i><br>
1.1 deraadt 185: A possible new security problem exists if you rely on securelevels and
186: immutable or append-only files or character devices. The fix does not
187: permit mmap'ing of immutable or append-only files which are otherwise
1.17 pvalchev 188: writable, as the VM system will bypass the meaning of the file flags
1.1 deraadt 189: when writes happen to the file.
1.50 sthen 190: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch">
1.1 deraadt 191: A source code patch exists which remedies this problem.</a>
192: <p>
1.31 henning 193: <li><a name="ipsec"></a>
1.64 deraadt 194: <font color="#009000"><strong>SECURITY FIX</strong></font>
195: <i>All architectures</i><br>
1.1 deraadt 196: If IPSEC communication is attempted by starting photurisd(8) (which is
197: disabled by default), a system crash may be evoked from remote if
198: an attacker uses some classes of invalid packets.
1.50 sthen 199: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch">
1.1 deraadt 200: A source code patch exists which remedies this problem.</a>
201: <p>
1.31 henning 202: <a name="xterm-xaw"></a>
1.64 deraadt 203: <li><font color="#009000"><strong>SECURITY FIX</strong></font>
204: <i>All architectures</i><br>
1.1 deraadt 205: As stated in CERT advisory VB-98.04, there are buffer
206: overrun problems in <strong>xterm</strong> related to the input-Method,
207: preeditType, and *Keymap resources. Additional buffer overruns exist in
208: the <strong>Xaw</strong> library related to the inputMethod and
209: preeditType resources. The xterm(1) problem represents a security
210: vulnerability for any platform where xterm is installed setuid-root
211: (as is the case for all OpenBSD platforms). The Xaw problem represents
212: a security vulnerability for any setuid-root program that uses the Xaw
213: library (including xterm). Patch1 from XFree86 3.3.2 corrects
214: these problems.
1.50 sthen 215: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/xterm-xaw.patch">
1.1 deraadt 216: We provide a version of this patch file specifically for the OpenBSD 2.3 tree</a>.
217: We also provide tar files which replace the xterm(1) binary and the libXaw
218: libraries on your system. These are expected to be extracted in
219: <strong>/usr/X11R6</strong> using the command
220: <strong>"tar xvfpz Xawfix.tgz"</strong>.
221: The files are...
1.50 sthen 222: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/Xawfix.tgz">i386</a>,
223: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/alpha/Xawfix.tgz">alpha</a>,
224: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mac68k/Xawfix.tgz">mac68k</a>,
225: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mvme68k/Xawfix.tgz">
1.1 deraadt 226: mvme68k</a>,
1.50 sthen 227: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/hp300/Xawfix.tgz">hp300</a>,
228: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/Xawfix.tgz">sparc</a>,
229: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/pmax/Xawfix.tgz">pmax</a>,
1.1 deraadt 230: and
1.50 sthen 231: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.
1.1 deraadt 232: <p>
1.31 henning 233: <li><a name="pctr"></a>
234: <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 235: The pctr(4) driver has bugs that permit any user to crash the machine,
236: if the CPU is not an Intel CPU. This problem has been properly fixed
237: since, but fixes are hard to apply to the 2.2 or 2.3 releases. To avoid
238: the problem, recompile your kernel without the pctr(4) device driver.
239: <p>
1.28 naddy 240: <li><font color="#009000"><strong>CORRUPTED FILE</strong></font><br>
1.1 deraadt 241: The CD version of the precompiled ghostscript package is corrupted and
242: not installable. The correct file can be retrieved by FTP from:
1.50 sthen 243: <a href="http://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz">
244: http://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz</a>.
1.1 deraadt 245: Its checksums (obtained with <i>cksum(1)</i>, <i>md5(1)</i> and
246: <i>sha1(1)</i> respectively) are:
247: <ul>
248: <li>725752890 3639338 ghostscript-5.10.tgz
249: <li>MD5 (ghostscript-5.10.tgz) = 3144ca814ad1965d671be2b7be3d3050
250: <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
251: </ul>
252: <p>
1.31 henning 253: <a name="pcvt"></a>
1.28 naddy 254: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 255: The pcvt(4) console driver has a bug that can cause some keyboard
256: controllers to lock up when a key is pressed that toggles the status
257: of a keyboard LED (scroll lock, caps lock, etc). The problem is
258: generally intermittent and the keyboard can be "unlocked" by unplugging
259: and plugging it back in.
1.50 sthen 260: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/pcvt.patch">
1.1 deraadt 261: A source code patch exists which remedies this problem.</a>
262: <p>
1.28 naddy 263: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 264: The 2.3 release does not run reliably on the sun4m LX/LC machines
265: (ie. Sparc Classic).
1.50 sthen 266: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/iommureg.patch">
1.1 deraadt 267: A source code patch exists which remedies this problem.</a>
268: Two kernels which replace the ones in the release are also provided:
1.50 sthen 269: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd">bsd</a> and
270: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd.scsi3">bsd.scsi3</a>.
1.1 deraadt 271: Other replacements for the 2.3 install tools are
1.50 sthen 272: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc">also available</a>.
1.1 deraadt 273: <p>
1.28 naddy 274: <li><font color="#009000"><strong>MINOR INCOMPATIBILITY</strong></font><br>
1.58 deraadt 275: The AmigaOS patch
1.1 deraadt 276: <a href="http://us.aminet.net/pub/aminet/util/sys/PoolMem.lha">PoolMem</a>
277: improves AmigaOS memory handling tremendously, but confuses loadbsd, which
278: grabs less memory from the system than is available. To work around the
279: problem, be sure to execute
280: <pre>
281: PoolMem remove
282: </pre>
283: right before running loadbsd. The next release of loadbsd will probably be
284: PoolMem-aware.
285: <p>
1.28 naddy 286: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 287: The XFree86 binary set shipped on the CD and FTP site are not the
288: exact final set that we shipped for the other releases. A few minor
289: changes, mostly in <strong>xdm(1)</strong> configuration, were made
290: after those binaries were made. Patches for this might come out later.
291: <p>
1.28 naddy 292: <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
1.1 deraadt 293: The XFree86 binary set was linked with an older version of the C
294: library. To work around the problem, do the following as root.
295: <p>
1.31 henning 296: <pre>
297: cd /usr/lib/
298: ln -s libc.so.18.0 libc.so.17
299: </pre>
1.1 deraadt 300: <p>
1.28 naddy 301: <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
1.1 deraadt 302: The X11R5 server used in this port does not understand the default
303: authorization types used by the X11R6 clients, which results in no
304: clients being able to connect to the server. To fix this
305: problem add the line below to /usr/X11R6/lib/X11/xdm/xdm-config.
306: <p>
1.31 henning 307: <pre>
308: DisplayManager._0.authName: MIT-MAGIC-COOKIE-1
309: </pre>
1.1 deraadt 310: <p>
1.28 naddy 311: <li><font color="#009000"><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.1 deraadt 312: The pmax install does not correctly install the boot block.
313: To work around the problem, after the install program has finished, do
314: the following (assuming scsi id 0):
315: <p>
1.31 henning 316: <pre>
317: disklabel rz0 > /tmp/label
318: disklabel -R -B rz0 /tmp/label
319: </pre>
1.1 deraadt 320: <p>
1.28 naddy 321: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 322: The XFree86 binary set shipped on the CD and FTP site are not the
323: exact final set that we shipped for the other releases. A few minor
324: changes, mostly in <strong>xdm(1)</strong> configuration, were made
325: after those binaries were made. Patches for this might come out later.
326: <p>
1.28 naddy 327: <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
1.1 deraadt 328: The XFree86 binary set was linked with an older version of the C
329: library. To work around the problem, do the following as root.
330: <p>
1.31 henning 331: <pre>
332: cd /usr/lib/
333: ln -s libc.so.18.0 libc.so.17
334: </pre>
1.1 deraadt 335: <p>
1.28 naddy 336: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 337: When you start the install an upgrade option is advertised but
338: there really is no such option.
339: <p>
1.28 naddy 340: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 341: When you start the install an upgrade option is advertised but
342: there really is no such option.
343: <p>
1.28 naddy 344: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.17 pvalchev 345: Unlabeled disks with weird geometries can panic the kernel.
1.1 deraadt 346: A fix will be made available when 2.3 is out.
347: <p>
1.28 naddy 348: <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 349: The powerpc release shipped on the OpenBSD 2.3 CD does not contain
350: two late fixes applied late in the release cycle. The
1.58 deraadt 351: <a href="errata22.html#rmjob">rmjob</a> and
1.28 naddy 352: <a href="errata22.html#uucpd">uucpd</a> patches should be applied to
1.1 deraadt 353: the system if those subsystems are used.
354: <p>
1.59 deraadt 355:
1.1 deraadt 356: </ul>
357:
358: </body>
359: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata23.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www