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