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