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