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