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