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