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