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