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