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