Annotation of www/errata22.html, Revision 1.30
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.19 deraadt 4: <title>OpenBSD 2.2 errata</title>
1.1 deraadt 5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="the OpenBSD CD errata page">
8: <meta name="keywords" content="openbsd,cd,errata">
9: <meta name="distribution" content="global">
1.27 jufi 10: <meta name="copyright" content="This document copyright 1997-2001 by OpenBSD.">
1.1 deraadt 11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
14:
1.10 pauls 15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
1.1 deraadt 16: <h2><font color=#0000e0>
1.14 espie 17: This is the OpenBSD 2.2 release errata & patch list:
1.1 deraadt 18: </font></h2>
19:
1.2 deraadt 20: <hr>
1.20 jason 21: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.2 deraadt 22: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
1.13 deraadt 23: <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
1.15 deraadt 24: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
1.18 deraadt 25: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
1.19 deraadt 26: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
1.22 deraadt 27: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
1.24 deraadt 28: <a href=errata28.html>For 2.8 errata, please refer here</a>.<br>
1.28 deraadt 29: <a href=errata29.html>For 2.9 errata, please refer here</a>.<br>
1.30 ! deraadt 30: <a href=errata30.html>For 3.0 errata, please refer here</a>.<br>
1.28 deraadt 31: <a href=errata.html>For 3.0 errata, please refer here</a>.<br>
1.2 deraadt 32: <hr>
33:
1.29 miod 34: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2.tar.gz>
1.11 deraadt 35: You can also fetch a tar.gz file containing all the following patches</a>.
36: This file is updated once a day.
37:
1.21 ericj 38: <p>
39: For more detailed information on install patches to OpenBSD, please
40: consult the <a href="./faq/faq10.html#10.14">OpenBSD FAQ</a>.
41:
1.11 deraadt 42: <hr>
43:
1.17 deraadt 44: <dl>
1.1 deraadt 45: <a name=all></a>
46: <li><h3><font color=#e00000>All architectures</font></h3>
47: <ul>
1.9 deraadt 48: <a name=ipsec></a>
1.5 matthieu 49: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.7 deraadt 50: If IPSEC communication is attempted by starting photurisd(8) (which is
1.8 deraadt 51: disabled by default), a system crash may be evoked from remote if
52: an attacker uses some classes of invalid packets.
1.7 deraadt 53: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch>
54: A source code patch exists which remedies this problem.</a>
1.9 deraadt 55: <p>
56: <a name=xterm-xaw></a>
1.7 deraadt 57: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.5 matthieu 58: As stated in CERT advisory VB-98.04, there are buffer
1.8 deraadt 59: overrun problems in <strong>xterm</strong> related to the input-Method,
60: preeditType, and *Keymap resources. Additional buffer overruns exist in
61: the <strong>Xaw</strong> library related to the inputMethod and
62: preeditType resources. The xterm(1) problem represents a security
63: vulnerability for any platform where xterm is installed setuid-root
64: (as is the case for all OpenBSD platforms). The Xaw problem represents
65: a security vulnerability for any setuid-root program that uses the Xaw
66: library (including xterm). Patch1 from XFree86 3.3.2 corrects
67: these problems.
1.5 matthieu 68: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/xterm-xaw.patch>
1.6 deraadt 69: We provide a version of this patch file specifically for the OpenBSD 2.2 tree</a>.
1.5 matthieu 70: <p>
1.1 deraadt 71: <a name=rmjob></a>
72: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
73: An exploitable buffer mismanagement exists in a subroutine used by
74: lprm and lpd. The problem is exploitable by users on a particular
75: machine if there is an entry in <strong>/etc/printcap</strong> which
76: points at a remote printer.
77: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rmjob.patch>
78: A patch is available which corrects this behaviour</a>.
79: <p>
80: <a name=uucpd></a>
81: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
82: A DNS-based vulnerability exists when uucpd is used. By default uucpd
83: is not enabled in the OpenBSD releases, but some sites may have enabled it.
84: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch>
85: A patch is available which corrects this behaviour</a>.
86: <p>
87: <a name=named></a>
88: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
89: A vulnerability exists when (and only when) /etc/named.conf has the
90: <strong>fake-iquery</strong> option enabled.
91: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch>
92: A patch is available which corrects this behaviour</a>.
93: <p>
94: <a name=ping></a>
95: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
96: A vulnerability exists in ping(8); if the -R option is used to record
97: routes, an attacker can spoof a reply packet that will overflow inside
98: ping. Preliminary investigation makes it look the worst attack
99: possible is to make ping crash, but one never knows...
100: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ping.patch>
101: A patch is available which corrects this behaviour</a>.
102: <p>
103: <a name=sourceroute></a>
1.23 jufi 104: <li><strong><font color=#009000>SECURITY FIX</font></strong><br>
1.1 deraadt 105: If the sysctl variable <strong>net.inet.ip.forwarding</strong> is
106: enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>
107: is disabled (value 0), the kernel will block source routed packets from
108: going through, but will still accept source routing packets destined for
109: itself. Our fix changes the <strong>net.inet.ip.sourceroute</strong>
110: variable semantics to mean that all source routed packets should
111: be blocked completely.
112: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/sourceroute.patch>
113: A kernel patch is provided</a>.
114: <p>
115: <a name=ruserok></a>
116: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
117: A combination localhost+remote host security problem exists if a
1.26 jsyn 118: local user running a setuid binary causes a non-existent root .rhosts
1.1 deraadt 119: file to be created via a symbolic link with a specific kind of corefile,
120: and then subsequently uses rsh/rlogin to enter the machine from remote.
121: A similar exploit might also be possible using sshd which lacks any code
122: for checking for deviations from the expected format in the .rhosts or
123: .shosts files, but we have not confirmed this yet. The following two
124: fixes are recommended:
125: <p>
126: <ul>
127: <li>
128: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch>
129: (1) A kernel patch which adds a new sysctl option which permits the
130: administrator to decide whether setuid corefiles should be written or not</a>.
131: <p>
132: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch>
133: (2) Replaces the libc ruserok() function with a more paranoid
134: version which detects bogus looking .rhosts files better.</a>
135: </ul>
136: <p>
137: If the
138: first patch is used to stop setuid coredumps, then the second patch is
139: not as important.
140: This problem is fixed much better in OpenBSD-current, where the kernel's
141: symbolic link handling has been improved such that coredumping will not
142: create a file on the other side of a symbolic link. Such a patch is not
143: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.<p>
144: The problem with the ruserok() function appears to also exist in
145: ssh 1.2.21 and previous (the ssh people have been alerted).
146: <p>
147: <a name=mmap></a>
1.23 jufi 148: <li><strong><font color=#009000>SECURITY FIX</font></strong><br>
1.1 deraadt 149: A bug in the vm system permits a file descriptor opened read-only on a
150: device, to later on be mmap(2)'d read-write, and then modified. This
151: does not result in a security hole by itself, but it does violate the
152: safety semantics which securelevels are supposed to provide. If a user
153: manages to gain kmem group permissions, using this problem they can then
154: gain root trivially and/or turn securelevels off.
155: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/vm_mmap.patch>
156: A kernel patch is available which corrects this behaviour (this is
157: revision 3 of this patch)</a>.
158: <p>
159: <li><font color=#009000><strong>BUILD PROCESS FIX</strong></font><br>
160: Building an object tree from a read-only source tree (such as off a CDROM)
161: may fail under certain circumstances (e.g. when creating a symlink on sparc
162: whose target name is exactly 33 characters). As a workaround you have to
163: either provide the source tree read/write, or install a newer version of
164: /usr/bin/readlink.
165: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/readlink.c>
166: A replacement source file exists</a>.
167: <p>
168: <a name=mountd></a>
169: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
170: If a line in /etc/exports which contains hostnames results in an empty
171: list because none of the supplied hostnames is known, mountd(8) will
172: accidentally export the filesystem to the world.
173: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch>
174: A patch is available which corrects this behaviour</a>.
175: <p>
176: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
177: Setting the MSG_EOR flag on a tcp packet in the send(2) family of
178: system calls could cause a kernel panic.
179: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch>
180: A patch</a> to return EINVAL in this case is available.
181: <p>
182: </ul>
183: <a name=i386></a>
184: <li><h3><font color=#e00000>i386</font></h3>
185: <ul>
186: <a name=f00f></a>
187: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
1.26 jsyn 188: The Intel P5 F00F bug was discovered after the CDRs had already been
1.1 deraadt 189: sent to the manufacturer. This problem permits any user who has an account
190: to lock your machine up using a 4-line program. The problem only affects
191: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
192: nor are processors by other manufacturers).
193: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch>
194: A kernel source-code patch is available</a>.
195: <p>
196: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
197: Some Linux binaries will execute in SVR4 emulation mode, which is
1.12 aaron 198: definitely a problem for people who need Linux emulation to work correctly.
1.1 deraadt 199: To solve this mis-identification problem,
200: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch>
201: a patch file is provided</a>.
202: <p>
203: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
204: APM can crash on machines without it.
205: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch>
206: A kernel source-code patch is available</a>.
207: <p>
208: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.25 pvalchev 209: A few people are running into this problem, particularly if they had some
1.1 deraadt 210: other *BSD operating system on their machine before trying OpenBSD: if after
211: installation onto an IDE-based machine, the kernel fails to mount the root
212: partition because it thinks that it should be opening sd0 (0x400), this means
213: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
214: is indicating that the drive is SCSI.
215: To repair this, use the floppy to run "disklabel -E wd0", then using the
216: "edit" command ensure the type field is set to "ST506".
217: <p>
218: </ul>
219: <a name=mac68k></a>
220: <li><h3><font color=#e00000>mac68k</font></h3>
221: <ul>
222: <li><font color=#009000><strong>NEW SOFTWARE</strong></font><br>
223: Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
224: CDROM. However, X11 for the mac68k is immediately available from
225: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
226: ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>. Please
227: be sure to read the <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/README.X11">README file</a> also in that directory for instructions on installing
228: and setting up X.
229: <p>
230: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
231: As shipped on the CDROM, both the
232: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
233: generic kernel</a>
234: and the
235: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/bsd-genericbsc.tar.gz">
236: genericsbc kernel</a>
237: extract themselves into the wrong place in the filesystem.
238: Both <strong>should</strong> extract a kernel named <tt>/bsd</tt>, but they extract
239: the kernel into <tt>/usr/src/sys/arch/mac68k/compile</tt> instead.
240: <p>
241: This has been fixed on the ftp release of <a href=22.html>OpenBSD 2.2</a>, and
242: fresh kernels are available from <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k">
243: ftp://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/</a>. If at all possible,
244: installing these kernels is recommended.
245: <p>
246: A number of possible workarounds exist if you don't have easy access to ftp
247: the updated kernels. The simplest of these is to use a
248: MacOS program to uncompress and untar the kernel aad use the Installer's
249: mini-shell to "cpin" the kernel. Alternately, you could install the kernel
250: with the Installer and use the mini-shell to move the binary from <tt>/usr/src/...</tt> to <tt>/bsd</tt>.
251: <p>
252: </ul>
253: <a name=sparc></a>
254: <li><h3><font color=#e00000>sparc</font></h3>
255: <ul>
256: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
1.25 pvalchev 257: Older 4/xxx systems (particularly the 4/300's) cannot boot
1.1 deraadt 258: with the 2.2 kernel due to bugs in the scsi device driver.
259: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch>
260: A kernel source patch is available</a>.
261: Replacement kernels are available for:
262: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd>bsd</a>,
263: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3>bsd.scsi3</a>,
264: and a replacement for bsd.rd is coming soon.
265: <p>
266: <a name=sparciommu></a>
267: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
268: SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
269: using a custom kernel configured for option sun4m only.
270: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch>
271: A workaround (kernel source patch) is available</a>. Apply the patch and
272: then re-build your kernel.
273: <p>
274: </ul>
275: <li><h3><font color=#e00000>amiga</font></h3>
276: <p>
277: <ul>
278: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
279: Missing Xamiga manual pages. Get
280: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz>
281: this package</a> and execute, <i>as root</i>:<br>
282: <strong><b># </b>pkg_add Xamiga-manual.tgz</strong><br>
283: The MD5 checksum of this package is:<br>
284: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b><p>
285: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
286: The Ariadne ethernet support was broken, there will be both binary and
287: source level fixes available shortly. If you are in a hurry mail
288: <a href=mailto:niklas@openbsd.org>Niklas</a> for a test kernel.<p>
289: </ul>
290: <a name=pmax></a>
291: <li><h3><font color=#e00000>pmax</font></h3>
292: <ul>
293: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
294: There is a Year-1998 problem in the time-setting code (which causes the
295: date and time to be set incorrectly after a reboot in 1998).
296: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch>
297: A source code patch file is available</a> plus replacement installation
298: kernels for the 2.2 release at
299: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS>bsd.NFS</a>,
300: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd>bsd</a>,
301: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0>bsd.rz0</a>.
302: <p>
303: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
304: X11 support for the 3min and 3maxplus machines was broken
305: due to a kernel bug.
306: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch>
307: A source code patch is available</a>.
308: <p>
309: <a name=ldso></a>
310: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
311: A security problem in the shared library linker <strong>ld.so</strong>
312: requires that you replace it with a new binary. The following binary
313: will work on both pmax and arc machines.
314: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so>
315: The replacement binary is here</a>.
316: <p>
317: </ul>
318: <a name=arc></a>
319: <li><h3><font color=#e00000>arc</font></h3>
320: <ul>
321: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
322: A security problem in the shared library linker <strong>ld.so</strong> requires
323: that you replace it with a new binary. The following binary
324: will work on both pmax and arc machines.
325: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so>
326: The replacement binary is here</a>.
327: <p>
328: </ul>
329: <li><h3><font color=#e00000>alpha</font></h3>
330: <p>
331: <ul>
332: <li><font color=#009000><strong>MISSING FUNCTIONALITY</strong></font><br>
1.4 deraadt 333: Network Address Translation and other parts of IP Filtering do not work
1.1 deraadt 334: on the alpha. This will be fixed in the 2.3 release, and perhaps earlier
335: in a snapshot. There is no patch for 2.2.
336: <p>
337: </ul>
338: <li><h3><font color=#e00000>hp300</font></h3>
339: <p>
340: <ul>
341: <li>No problems identified yet.
342: <p>
343: </ul>
344: <li><h3><font color=#e00000>mvme68k</font></h3>
345: <ul>
346: <li>No problems identified yet.
347: <p>
348: </ul>
1.17 deraadt 349:
350: </dl>
1.1 deraadt 351: <br>
352:
353: <hr>
1.20 jason 354: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.3 deraadt 355: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
1.13 deraadt 356: <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
1.15 deraadt 357: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
1.18 deraadt 358: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
1.19 deraadt 359: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
1.22 deraadt 360: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
1.24 deraadt 361: <a href=errata28.html>For 2.8 errata, please refer here</a>.<br>
1.28 deraadt 362: <a href=errata29.html>For 2.9 errata, please refer here</a>.<br>
1.30 ! deraadt 363: <a href=errata30.html>For 3.0 errata, please refer here</a>.<br>
1.28 deraadt 364: <a href=errata.html>For 3.0 errata, please refer here</a>.<br>
1.1 deraadt 365: <hr>
1.2 deraadt 366:
1.16 deraadt 367: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.1 deraadt 368: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.30 ! deraadt 369: <br><small>$OpenBSD: errata22.html,v 1.29 2001/10/22 22:20:49 miod Exp $</small>
1.1 deraadt 370:
371: </body>
372: </html>