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