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