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