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