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