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