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