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