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