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